As Tair and Redis Open-Source Edition evolve through version iterations, newer versions typically provide higher performance, enhanced security and stability, and more features. In addition, newer versions generally receive more technical support. If you want to use a new version, you can upgrade the major version of your instance by using the console or by calling an API operation, rather than creating an additional instance.
Impacts
When you apply for resources, upgrade the replica node, or synchronize data, the service remains available.
When you switch your workloads from the original instance over to a new instance or from the master node over to the replica node in the original instance, you may experience transient connections that last for a few seconds. The original instance stays in the read-only state for up to 60 seconds until all data is synchronized. We recommend that you upgrade the original instance during off-peak hours.
After the upgrade is complete, the instance ID, endpoints, data, whitelists, accounts, and account passwords remain unchanged. Make sure that your application can automatically reconnect to your instance.
If the original instance is a Redis Open-Source Edition 4.0 instance, Bloom filter-related API operations such as BF.ADD are no longer supported after you upgrade the original instance to a major version later than Redis 4.0.
NoteBloom filter-related API operations are for internal use only in existing instances that run Redis 4.0 and are no longer available for new instances that run Redis 4.0 or later. If you call Bloom filter-related API operations on the new instances, unknown risks such as cache analysis failures may occur. We recommend that you change the original instance into a Tair DRAM-based instance to use the optimized Bloom filters.
Precautions
You can upgrade the major version of an instance only within the same deployment mode. For example, Redis Open-Source Edition 5.0 instances deployed in classic mode cannot be upgraded to Redis Open-Source Edition 6.0 instances deployed in cloud-native mode.
If Data Transmission Service (DTS) tasks are created for the instance for which you want to upgrade the major version, the upgrade fails. Stop the DTS tasks and try again.
If you upgrade the major version of a classic cluster instance that has a private endpoint, the
The direct custins tranfer does not support upgrade major versionerror message is returned. Release the private endpoint and try again.If the classic network endpoint of the instance is not released, the upgrade may fail. Release the classic network endpoint and try again. After you release the classic network endpoint, you cannot reapply for it. We recommend that you use a virtual private network (VPC) for faster transmission and higher security.
If you upgrade the major version of an instance, the memory usage of the instance may change slightly in the range of approximately -10% to 10%. The specific change depends on the differences in how different versions store metadata. We recommend that you make sure that the memory usage of the instance is less than 80% before you upgrade the major version. This prevents the memory usage of the instance from reaching a high level after the major version is upgraded.
Procedure
Log on to the ApsaraDB for Redis console and go to the Instances page. In the top navigation bar, select the region in which the instance is deployed. Then, find the instance and click its ID.
In the Configuration Information section, choose to the right of Version.
NoteIf the Major Version Upgrade menu item is not displayed, the major version of the instance cannot be upgraded.
In the panel that appears, specify the new major version and the time when you want to perform the upgrade.
WarningDuring instance upgrades or master-replica switchovers, an instance experiences transient connections that last for a few seconds and remains read-only for up to 60 seconds. To minimize impacts, we recommend you select Update During Maintenance. This way, the system performs the operation during the maintenance window. For information about how to modify the maintenance window, see Configure a maintenance window.
Click OK.
Related API operations
API operation | Description |
Upgrades the major version of an instance. |
FAQ
Why does the status of an instance change to Upgrading Major Version after I select Update During Maintenance to upgrade the major version?
The status of an instance changes to Upgrading Major Version because the system is preparing for the upgrade. During the preparation, the instance service remains available. When the system prepares for upgrades, such as applying for resources and synchronizing data, instance switchovers or master-replica switchovers are not performed and services provided are not affected.
NoteThe instance experiences transient connections that last for a few seconds and remains read-only for up to 60 seconds only during instance switchovers or master-replica switchovers.
Why does a major version upgrade of an instance fail?
This may be because the instance is of a retired instance type. For information about retired instance types, see Phased-out specifications. Switch the instance to an available instance type and then upgrade the major version. You can switch the instance to an available instance type that has the same memory size as the current instance type.
To which version can Redis Open-Source Edition 2.8 instances be upgraded?
Redis Open-Source Edition 2.8 instances can be upgraded only to Redis Open-Source Edition 5.0 instances.