Skip to content

Commit a3a0fa6

Browse files
committed
Made fixes to text for Acrolinx, etc. added links
1 parent 31a50d9 commit a3a0fa6

File tree

1 file changed

+19
-16
lines changed

1 file changed

+19
-16
lines changed

articles/azure-cache-for-redis/cache-retired-features.md

Lines changed: 19 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: flang-msft
77
ms.author: franlanglois
88
ms.service: cache
99
ms.topic: conceptual
10-
ms.date: 09/30/2022
10+
ms.date: 12/08/2022
1111

1212
---
1313

@@ -40,7 +40,7 @@ From now through 30 June 2023, you can continue to use existing Azure Cache for
4040

4141
### Version 4 caches on cloud services
4242

43-
If your cache instance is affected by the Cloud Service retirement, you're unable to upgrade to Redis 6 until after you migrate to a cache built on virtual machine scale set. In this case, send mail to [email protected], and we'll help you with the migration.
43+
If your cache instance is affected by the Cloud Service retirement, you're unable to upgrade to Redis 6 until after you migrate to a cache built on Virtual Machine Scale Set. In this case, send mail to [email protected], and we'll help you with the migration.
4444

4545
For more information on what to do if your cache is on Cloud Services (classic), see [Azure Cache for Redis on Cloud Services (classic)](cache-faq.yml#what-should-i-do-with-any-instances-of-azure-cache-for-redis-that-depend-on-cloud-services--classic-).
4646

@@ -52,57 +52,60 @@ You check the Redis version of your cache instance by selecting **Properties** f
5252

5353
### Why is Redis version 4 being retired?
5454

55-
Azure Cache for Redis is the managed offering for the popular open-source caching solution Redis. Redis version 4 is no longer supported by the open source community and will no longer be supported on Azure starting June 30, 2023.
55+
Azure Cache for Redis is the managed offering for the popular open-source caching solution Redis. Redis version 4 is no longer supported by the open-source community. Redis 4 will no longer be supported on Azure starting June 30, 2023.
5656

5757
### Will Redis 4 caches be supported until retirement?
5858

5959
Redis version 4 caches continues to get critical bug fixes and security updates until June 20, 2023.
6060

6161
### My Redis 4 caches are linked with geo-replication link. What happens to the geo-replication link during upgrade?
6262

63-
Caches can't be upgrade while they have a geo-replication link. First, you must unlink the caches temporarily, upgrade both your caches, and then re-link them.
63+
Caches can't be upgraded while they have a geo-replication link.
6464

65-
### What happens to my cache if I do not upgrade to Redis version 6 by June 30, 2023?
65+
1. First, you must unlink the caches temporarily.
66+
1. Upgrade both your caches.
67+
1. Then relink them.
6668

67-
If you do not upgrade your Redis 4 cache by June 30, 2023, the cache is automatically upgraded to version 6. If you have a maintenance window scheduled for your cache, the upgrade happens during the maintenance window. Geo-replicated caches will be retired on August 20, 2023.
69+
### What happens to my cache if I don't upgrade to Redis version 6 by June 30, 2023?
6870

69-
### What happens to my CloudService cache if I do not upgrade it by June 30, 2023?
71+
If you don't upgrade your Redis 4 cache by June 30, 2023, the cache is automatically upgraded to version 6. If you have a maintenance window scheduled for your cache, the upgrade happens during the maintenance window. Geo-replicated Redis 4 caches will be retired on August 20, 2023.
7072

71-
Cloud Service version 4 caches can't be upgraded to version 6 until they are migrated to a cache based on Azure Virtual Machine Scale Set.
73+
### What happens to my Cloud Service cache if I don't upgrade it by June 30, 2023?
7274

73-
For more information, see <Azure Cache for Redis FAQ - Azure Cache for Redis | Microsoft Learn> for more details.
75+
Cloud Service version 4 caches can't be upgraded to version 6 until they're migrated to a cache based on Azure Virtual Machine Scale Set.
7476

75-
As documented <> starting April 30, 2023, Cloud Service caches receive only critical security updates and critical bug fixes. Cloud Service caches will not support any new features released after APril 20,2023 and we highly recommend migrating your caches to Azure Virtual Machine Scale Set.
77+
For more information, see [Caches with a dependency on Cloud Services (classic)](/azure/azure-cache-for-redis/cache-faq).
78+
79+
Starting on April 30, 2023, Cloud Service caches receive only critical security updates and critical bug fixes. Cloud Service caches won't support any new features released after April 20, 2023. We highly recommend migrating your caches to Azure Virtual Machine Scale Set.
7680

7781
### Do I need to update my application to be able to use Redis version 6?
7882

7983
Redis version 6 is compatible with version 4 and applications should continue to function seamlessly after the version upgrade.
8084

8185
### What exactly happens to my cache when I execute the upgrade operation?
8286

83-
During the upgrade process, the replica node of your cache is first upgraded to run Redis version 6. The upgrade replica node then takes over as the primary node for your cache while the former primary node reboots to take on the role of replica. This is exactly like the patching process described here: Failover and patching - Azure Cache for Redis | Microsoft Learn and results in a failover.
87+
During the upgrade process, the replica node of your cache is first upgraded to run Redis version 6. The upgrade replica node then takes over as the primary node for your cache while the former primary node reboots to take on the role of replica. This process is exactly like the patching process described in [How does patching occur?](cache-failover.md#how-does-patching-occur).
8488

8589
### Will my cache be available during the upgrade process?
8690

87-
Standard and Premium caches are fully functional and available during the upgrade process, but your applications sees a connection blip for a few seconds. Basic caches are unavailable during the upgrade and all data will be lost.
91+
Standard and Premium caches are fully functional and available during the upgrade process, but your applications see a connection blip for a few seconds. Basic caches are unavailable during the upgrade and all data will be lost.
8892

8993
### How long does the upgrade operation last?
9094

9195
Typically, the upgrade operation takes about 20 minutes per cache node, but it could take longer if the cache is under high server load.
9296

9397
### Can I execute upgrade operation through REST API, Azure CLI or PowerShell?
9498

95-
Yes, the upgrade process can be triggered through REST API, Azure CLI or PowerShell command. For more information, see How to upgrade the Redis version of Azure Cache for Redis | Microsoft Learn
99+
Yes, the upgrade process can be triggered through REST API, Azure CLI or PowerShell command. For more information, see [How to upgrade an existing Redis 4 cache to Redis 6](cache-how-to-upgrade.md).
96100

97101
### Is my application affected during upgrade?
98102

99-
Your application sees a connection blip that lasts a few seconds. Your application should retry commands appropriately on experiencing connectivity errors. Fore more information, see Best practices for connection resilience - Azure Cache for Redis | Microsoft Learn
103+
Your application sees a connection blip that lasts a few seconds. Your application should retry commands appropriately when experiencing connectivity errors. Fore more information, see [Best practices for connection resilience](cache-best-practices-connection.md).
100104

101-
### Can I rollback the upgrade operation?
105+
### Can I roll back the upgrade operation?
102106

103107
No, the upgrade can't be rolled back.
104108

105-
106109
## Next steps
107110
<!-- Add a context sentence for the following links -->
108111
- [What's new](cache-whats-new.md)

0 commit comments

Comments
 (0)