This topic describes how to upgrade the major version of an ApsaraDB for Redis instance in the ApsaraDB for Redis console to use the features of the new major version. For example, you can upgrade the major version from Redis 2.8 to Redis 4.0.
The upgrade workflow varies based on the instance architecture. For more information, see the following table.
Workflow (performed in the background)
When you apply for resources, upgrade the replica node, or synchronize data, your ApsaraDB for Redis 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, endpoint, data, whitelist settings, accounts, and account passwords remain unchanged. Make sure that your application is configured to automatically re-connect to your instance.
If the original instance runs Redis 4.0, Bloom filter-related API operations such as BF.ADD are no longer supported after you upgrade the major version of the original instance to a version later than Redis 4.0.Note
Bloom 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 an Enhanced Edition (Tair) DRAM-based instance to use the optimized Bloom filters. For more information about DRAM-based instances, see DRAM-based instances.
You can upgrade the major version only for Community Edition instances that are deployed in classic mode. Tair instances do not require major version upgrades.
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.
When you upgrade the major version for a classic cluster instance that has a private endpoint, the
The direct custins tranfer does not support upgrade major versionerror is reported. Release the private endpoint and try again.
- 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 Basic information section, click Major Update.Note
If the Major Update button does not exist, you are using the latest major version.
In the panel that appears, specify the new major version and the time when you want to perform the upgrade.Warning
During 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 more information about how to modify the maintenance window, see Set a maintenance window.
Related API operations
Upgrades the major version of an ApsaraDB for Redis instance.
Why does the state of an instance change to Upgrading Major Version after I select Update During Maintenance to upgrade the major version?
The state 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.Note
The instance experiences transient connections for a few seconds and then remains in the read-only state 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. Change the instance to an available instance type and then upgrade the major version. You change the instance to an available instance type that has the same memory size as the current instance type.