Skip to content

Commit 394f814

Browse files
committed
tweaks for style, added review feeadback
1 parent e6abfa9 commit 394f814

1 file changed

Lines changed: 1 addition & 2 deletions

File tree

articles/redis/failover.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,11 +55,10 @@ The Azure Managed Redis service regularly updates your cache with the latest pla
5555
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.
5656
4. Finally, all VMs that were replaced are deleted.
5757

58-
5958
Each shard of a clustered cache is patched separately and doesn't close connections to another shard.
6059

6160
> [!NOTE]
62-
> Multiple caches in the same region may be patched at the same time, even if they exist in the same subscription and resource group. If this impacts your application, configure [maintenance schedules](scheduled-maintenance.md) such that each cache is patched at a different time.
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.
6362
6463
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).
6564

0 commit comments

Comments
 (0)