You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/redis/failover.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,10 +55,10 @@ The Azure Managed Redis service regularly updates your cache with the latest pla
55
55
3. One by one, all nodes being patched are removed from the cluster. Any shards on these VMs will be demoted and migrated to one of the new VMs.
56
56
4. Finally, all VMs that were replaced are deleted.
57
57
58
-
59
58
Each shard of a clustered cache is patched separately and doesn't close connections to another shard.
60
59
61
-
Multiple caches in the same resource group and region are also patched one at a time. Caches that are in different resource groups or different regions might be patched simultaneously.
60
+
> [!NOTE]
61
+
> Multiple caches in the same region might be patched at the same time. If this affects your application, configure [maintenance schedules](scheduled-maintenance.md) such that each cache is patched at a different time.
62
62
63
63
Because full data synchronization happens before the process repeats, data loss is unlikely to occur for your cache. You can further guard against data loss by [exporting](how-to-import-export-data.md#export) data and enabling [persistence](how-to-persistence.md).
0 commit comments