Stay organized with collections
Save and categorize content based on your preferences.
This page describes how your Memorystore instance behaves during a version
upgrade operation, how an upgrade operation can affect your application, and
when you should run an upgrade operation. To learn how to upgrade an instance's
Redis version, see Upgrading an instance's Redis version.
Depending on the instance's tier,
running a version upgrade operation can have performance and storage
implications for your application. There are also some limitations to upgrading
instances based on the amount of memory that is currently in use.
Best practices for upgrading an instance's Redis version
We recommend that you upgrade to version 7.0 and later because Certificate Authority rotation no longer drops connections.
We recommend exporting
your instance data before running a version upgrade operation.
For Standard Tier instances, to increase the speed and reliability of
your version upgrade operation, upgrade your instance during periods of low
instance traffic. To learn how to monitor instance traffic, see
Monitoring Redis instances.
When upgrading a Standard Tier instance, keep the instance write load to a
minimum. A high write load can cause upgrade operations to take significantly
longer, and can cause upgrades to fail.
Version upgrade behavior
Data is preserved during a version upgrade operation for both Basic and Standard Tier instances. During an upgrade operation the instance undergoes a short connection reset of a couple minutes, or less. Applications should incorporate retry logic in the code to be able to reconnect to the instance. The IP address and connection string remain the same.
Because of the short term connection break, there may be a small amount of stale or inconsistent data that didn't write or update to the cache for the short amount of time the instance was unavailable.
Write load during an upgrade
You should upgrade an instance during a period of low instance traffic to minimize the performance impact on your application. A high write load, or high memory pressure, can cause an upgrade operation to take significantly longer and can cause the upgrade to fail. For more information see Scaling and version upgrade operations.
Expired keys
When you upgrade a Standard Tier instance, expired keys are not synced. If you have expired keys in your Redis instance before you upgrade, you will have fewer keys after the instance is upgraded.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# About upgrading the Redis version of an instance\n\nThis page describes how your Memorystore instance behaves during a version\nupgrade operation, how an upgrade operation can affect your application, and\nwhen you should run an upgrade operation. To learn how to upgrade an instance's\nRedis version, see [Upgrading an instance's Redis version](/memorystore/docs/redis/upgrading-instance-version).\n\nDepending on the instance's [tier](/memorystore/docs/redis/redis-tiers),\nrunning a version upgrade operation can have performance and storage\nimplications for your application. There are also some limitations to upgrading\ninstances based on the amount of memory that is currently in use.\n\nBest practices for upgrading an instance's Redis version\n--------------------------------------------------------\n\n- We recommend that you upgrade to version 7.0 and later because [Certificate Authority rotation](/memorystore/docs/redis/about-in-transit-encryption#certificate_authority_rotation) no longer drops connections.\n\n- We recommend [exporting](/memorystore/docs/redis/export-data)\n your instance data before running a version upgrade operation.\n\n- For Standard Tier instances, to increase the speed and reliability of\n your version upgrade operation, upgrade your instance during periods of low\n instance traffic. To learn how to monitor instance traffic, see\n [Monitoring Redis instances](/memorystore/docs/redis/monitoring-instances).\n\n- When upgrading a Standard Tier instance, keep the instance write load to a\n minimum. A high write load can cause upgrade operations to take significantly\n longer, and can cause upgrades to fail.\n\nVersion upgrade behavior\n------------------------\n\nData is preserved during a version upgrade operation for both Basic and Standard Tier instances. During an upgrade operation the instance undergoes a short connection reset of a couple minutes, or less. Applications should incorporate retry logic in the code to be able to reconnect to the instance. The IP address and connection string remain the same.\n\nBecause of the short term connection break, there may be a small amount of stale or inconsistent data that didn't write or update to the cache for the short amount of time the instance was unavailable.\n\n### Write load during an upgrade\n\nYou should upgrade an instance during a period of low instance traffic to minimize the performance impact on your application. A high write load, or high memory pressure, can cause an upgrade operation to take significantly longer and can cause the upgrade to fail. For more information see [Scaling and version upgrade operations](/memorystore/docs/redis/memory-management-best-practices#scaling_and_version_upgrade_operations).\n\n### Expired keys\n\nWhen you upgrade a Standard Tier instance, expired keys are not synced. If you have expired keys in your Redis instance before you upgrade, you will have fewer keys after the instance is upgraded."]]