A maintenance window allows you to control the day(s) and time(s) of a week during which the VM(s) hosting your cache can be updated. On the left, Schedule updates allows you to choose a maintenance window for your cache instance. You don't see Reboot when using a cache from the Enterprise tier. Reboot is available for Basic, Standard and Premium tiers.The settings that you see on the Resource menu under Administration depend on the tier of your cache. Reboot isn't available for the Enterprise tier yet. Yes, for PowerShell instructions see To reboot an Azure Cache for Redis. For more information about possible causes for data loss, see What happened to my data in Redis? Can I reboot my cache using PowerShell, CLI, or other management tools? Another scenario for data loss would be if you reboot one node and the other node happens to go down because of a failure at the same time. For example if the primary node is rebooted and a cache write is in progress, the data from the cache write is lost. If you reboot just one of the nodes, data isn't typically lost, but it still might be. However, any cache writes that have occurred after the backup was made are lost. If you have configured data persistence, the most recent backup is restored when the cache comes back online. However, the data might not be lost either.
If you reboot both the Master and Replica nodes, all data in the cache (or in that shard when you're using a premium cache with clustering enabled) might be lost. Will I lose data from my cache if I do a reboot? If the underlying issue is not resolved, the client connections may continue to be used up. If you reboot your cache to clear client connections, StackExchange.Redis automatically reconnects once the Redis node is back online. Rebooting the cache provides a way to clear all client connections. Each pricing tier has different client connection limits for the various sizes, and once these limits are reached, no more client connections are accepted. Rebooting can be useful in the case where each client connection is used up because of a logic error or a bug in the client application. Yes, if you reboot the cache, all client connections are cleared. Can I reboot the cache to clear client connections? To test the resiliency of your application against total failure of the cache, reboot Both nodes. To test the resiliency of your application against failure of the replica node, reboot the Replica node. To test the resiliency of your application against failure of the primary node of your cache, reboot the Master node. Which node should I reboot to test my application?
Both primary and replica - When both cache nodes are rebooted, you lose all data in the cache and connections to the cache fail until the primary node comes back online.Replica - When the replica node is rebooted, there's typically no effect on the cache clients.
During this failover, there may be a short interval in which connections may fail to the cache.
The effect on your client applications varies depending on which nodes you reboot. After a few minutes, the selected nodes reboot, and are back online a few minutes later. If you have a premium cache with clustering enabled, select the shards to reboot, and then select Reboot. To reboot one or more nodes of your cache, select the nodes and select Reboot. If you have a premium cache with clustering enabled, you can select which shards of the cache to reboot. Select the nodes to reboot and select Reboot. Reboot is not yet available for the Enterprise tier.