Skip to content

Commit 738fc8a

Browse files
Merge pull request #218669 from flang-msft/fxl---Clarify-patching-documentation
fxl---Clarifying order of patching on nodes
2 parents 9cf6c33 + 840d68f commit 738fc8a

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

articles/azure-cache-for-redis/cache-failover.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,12 @@
22
title: Failover and patching - Azure Cache for Redis
33
description: Learn about failover, patching, and the update process for Azure Cache for Redis.
44
author: flang-msft
5+
56
ms.author: franlanglois
67
ms.service: cache
78
ms.topic: conceptual
89
ms.date: 11/16/2022
10+
ms.custom: engagement-fy23
911

1012
---
1113

@@ -49,8 +51,7 @@ An *unplanned failover* might happen because of hardware failure, network failur
4951

5052
The Azure Cache for Redis service regularly updates your cache with the latest platform features and fixes. To patch a cache, the service follows these steps:
5153

52-
1. The management service selects the node to be patched.
53-
1. The replica node is patched.
54+
1. The service patches the replica node first.
5455
1. The patched replica cooperatively promotes itself to primary. This promotion is considered a planned failover.
5556
1. The former primary node reboots to take the new changes and comes back up as a replica node.
5657
1. The replica node connects to the primary node and synchronizes data.

articles/azure-cache-for-redis/cache-how-to-upgrade.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,7 @@ ms.author: franlanglois
77
ms.service: cache
88
ms.topic: how-to
99
ms.date: 11/16/2022
10-
ms.custom: template-how-to
11-
10+
ms.custom: template-how-to, engagement-fy23
1211
---
1312

1413

@@ -32,7 +31,7 @@ For more details on how to export, see [Import and Export data in Azure Cache fo
3231

3332
### Limitations
3433

35-
- Upgrading a Basic tier cache results in brief unavailability and data loss.
34+
- When you upgrade a cache in the Basic tier, it is unavailable for several minutes and results in data loss.
3635
- Upgrading on geo-replicated cache isn't supported. You must manually unlink the cache instances before upgrading.
3736
- Upgrading a cache with a dependency on Cloud Services isn't supported. You should migrate your cache instance to virtual machine scale set before upgrading. For more information, see [Caches with a dependency on Cloud Services (classic)](./cache-faq.yml) for details on cloud services hosted caches.
3837

0 commit comments

Comments
 (0)