ApsaraDB for Redis continuously undergoes deep optimizations of its database kernel and proxy nodes to provide more features or fix known issues, ultimately improving the overall stability of the service. You can easily update the database kernel and proxy nodes to the latest version in the console. You can also configure automatic update policies based on your specific requirements.
When you update the database version of an instance, Redis first updates the replica instance or prepares a new instance. When the specified execution time arrives, the system performs a master/replica switchover or instance switchover to complete the update. During the switchover, the instance experiences transient connections that last for a few seconds and remains read-only for up to 60 seconds until all data is synchronized. Make sure that your application can automatically reconnect to the instance.
When you update the minor version of proxy nodes, Redis uses the hot update technology. This way, the new version of the proxy nodes leverages the client connection information from the old version to restore the connections. This enables uninterrupted connections with minimal millisecond-level latency fluctuations. However, specific types of commands, such as BLOCK, Transactions, and Pub/Sub, may experience interruptions during the update. Make sure that your business logic has appropriate reconnection mechanisms for these commands. If a client uses a private endpoint to connect to the Redis instance, all commands remain unaffected during the update.
Canary release of later minor versions may be available only in specific regions. The system checks the minor version of your instance. If your instance is of the latest minor version, the Minor Version Upgrade or Upgrade Proxy button is not displayed or is unavailable in the Tair console.
Unless otherwise stated, Alibaba Cloud ensures compatibility between the minor engine versions of Redis. You do not need to worry about compatibility issues that may be caused by updates. For more information, see Release notes for minor versions of ApsaraDB for Redis Enhanced Edition (Tair), Release notes for minor versions of ApsaraDB for Redis Community Edition, and Release notes for minor versions of ApsaraDB for Redis proxy nodes.
After you update the minor version of an instance, the instance information that includes the endpoints, data, whitelists, and existing accounts and their corresponding passwords does not change. However, we recommend the following suggestions:
Perform the update during off-peak hours.
Make sure that your application can automatically reconnect to the instance.
Update level description
The icon changes colors based on the minor version update level. The update level is displayed in green, yellow, or red to represent the regular, recommended, or critical update.
Regular update. This update level includes routine feature updates, such as adding a feature. We recommend that you perform LOW-level updates within 90 days.
Recommended update. This update level includes optimization of features and modules. LOW-level updates are also included in MEDIUM-level updates. We recommend that you perform MEDIUM-level updates within 60 days.
Critical update. This update level includes major updates that ensure stability or security, such as fixing a vulnerability or defect. LOW-level and MEDIUM-level updates are also included in HIGH-level updates. We recommend that you perform HIGH-level updates within 14 days.
Configure automatic update
Version Management Center allows you to check information about the version status of each instance, including whether the latest version is used. You can also use this feature to update instance versions or configure automatic update policies. This feature helps you manage instance versions in a centralized manner.
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 that you want to manage resides.
In the left-side navigation pane, click Version Management Center.
In the upper-left corner of the console, select a region.
On the Version Management Center page, you can view the current minor version and whether it is the latest minor version for all instances in the current region.
Click Configure in the Actions column corresponding to the instance that you want to manage. In the Configure dialog box, turn on Automatic Update to configure automatic update operations.
After you turn on Automatic Update, the system checks the instance versions on a regular basis. If a new version is identified, the system updates the instance to the new version during the specified Update Period within seven days.
The update period of an instance is the same as the maintenance window of the instance. If you modify one of the periods, the modification is automatically synchronized to the other period.Note
You can select multiple instances and batch perform Update or Configure operations on the instances.
You can chooseto query the version update records of instances.
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 that you want to manage resides. Then, find the instance and click the instance ID.
In the Basic information section, move the pointer over the icon next to Minor Version Upgrade or Upgrade Proxy to view the current minor version, the minor version to which you want to update, and the release notes of minor versions.
After you view the release notes of minor versions, click Minor Version Upgrade or Upgrade Proxy.
In the panel that appears, specify the time when you want to perform the update.
Why does the status of an instance change to Upgrading Minor Version after I select Update During Maintenance to update the minor version?
The status of an instance changes to Upgrading Minor Version because the instance is preparing for the update. When the system prepares for updates, such as applying for resources and synchronizing data, instance switchovers or master/replica switchovers are not performed, and service availability is not affected. The 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 is the Minor Version Upgrade button not displayed in the console?
The Minor Version Upgrade button is not displayed in the console because the current minor version of your instance is already up to date.
Related API operations
Queries the major version and minor version of an ApsaraDB for Redis instance and the release notes for minor versions.
Updates the minor version of an ApsaraDB for Redis instance.