ApsaraDB for Tair (compatible with Redis) continuously enhances its database kernel and proxy nodes to add features, fix issues, and improve stability. You can upgrade these components to the latest version in the console with a single click or configure an automatic upgrade policy.
Considerations
When you upgrade the database version, the system first upgrades the replica instance or prepares a new one. At the scheduled time, a switchover occurs to complete the upgrade. During this process, the instance enters a read-only state for up to 60 seconds while data is fully synchronized, and a brief connection interruption occurs. Ensure your application has a reconnection mechanism.
Upgrading the proxy version:
For a cloud-native edition instance, the proxy nodes are restarted sequentially, and all connections are dropped. Ensure that your application has a reconnection mechanism.
For a classic edition instance, a hot upgrade is performed. New proxy nodes restore client connections using information from the old nodes. This process avoids connection drops, but millisecond-level latency jitter may occur. However, commands such as BLOCK, Transactions, and Pub/Sub will be interrupted. Ensure that your application includes a reconnection mechanism for these commands. If your client connects to the instance using a direct connection address, all commands are unaffected.
Newer minor versions may be released on a canary basis in specific regions. The system automatically detects the minor version of your instance. If the Minor Version Upgrade and Proxy Version Upgrade buttons in the console are disabled, your instance is already up to date.
Unless otherwise specified, minor versions of the instance kernel are backward-compatible, so you can upgrade without compatibility concerns. For more information, see the Tair Minor Version Release Notes, Redis Community Minor Version Release Notes, and Proxy Minor Version Release Notes.
Upgrading the minor version does not change the instance's endpoint, data, IP address whitelist, or other configuration settings, such as accounts and passwords. However, we recommend that you:
Perform upgrades during off-peak hours.
Ensure that your application has a reconnection mechanism.
Update levels
LOW: regular updates. LOW-level updates include routine feature updates, such as adding a feature.
MEDIUM: recommended updates. MEDIUM-level updates include optimization of features and modules. LOW-level updates are also included in MEDIUM-level updates.
HIGH: major updates. HIGH-level updates include 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.
Configure automatic upgrades
In the Version Management Center, you can view the version status of each instance, including whether they are up to date. This feature also allows you to configure automatic upgrade policies and centrally manage all instance versions.
Log on to the 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 navigation pane on the left, click Version Management Center.
In the upper-left corner of the page, select the target region.
On the Version Management Center page, you can view information for all instances in the current region, such as the Current Minor Version and whether it is the Latest Minor Version.
Click Configure next to the instance and turn on the Automatic Update switch.
After this feature is enabled, the system periodically checks for new versions. If a new version is found, an automatic upgrade is scheduled within a Update Period in the next 60 days. In special cases, such as a high number of recent operational events for the same account, the upgrade may be postponed.
The Update Period is the same as the instance's Maintenance Window, and modifying either setting updates the other.
NoteYou can select multiple instances to perform Update or Configure operations in batches.
You can view the upgrade history of an instance in the .
Manual upgrade
Log on to the 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 Configuration Information section, hover over the tooltip icon next to Version or Proxy Version to view the release notes for that version.
After you review the release notes, click or .
NoteIf the Minor Version Upgrade or Proxy Version Upgrade button is disabled, the instance is already running the latest version and does not need to be upgraded.
In the panel that appears, select an upgrade time.
Click OK.
FAQ
Q: How can I confirm if my Tair instance is running the latest minor version?
A: If the Minor Version Upgrade or Proxy Version Upgrade button is grayed out, your instance is up to date. If a panel appears after you click the button, your instance is not on the latest version, and you can follow the steps in this topic to upgrade it.
Q: Can I upgrade to a specific minor version?
A: No, you cannot specify a minor version. By default, the system upgrades to the latest minor version. All minor versions are backward-compatible, so you do not need to worry about compatibility issues.
Q: I chose the Update During Maintenance option. Why did my instance status still change to 'Upgrading Minor Version'?
A: The system is performing preparatory tasks for the upgrade, such as requesting resources and synchronizing data. This phase does not involve a switchover and will not affect your service. The instance enters a read-only state for up to 60 seconds and experiences a brief connection interruption only during the actual switchover.
Q: After I changed my instance's upgrade policy to Automatic Update, why has it not been upgraded yet?
A: The upgrade does not happen immediately. The system periodically checks for new versions. If a new version is found, an automatic upgrade is scheduled within a maintenance window in the next 60 days. In special cases, such as a high volume of recent operational events for the account, the upgrade may be postponed. You can check the upgrade schedule in the event center or perform a manual upgrade immediately.
Q: Why do I still receive event notifications for minor version upgrades even if I chose manual upgrades?
A: Manual upgrades only disable the automatic minor version upgrade service. However, if the version has a high-risk vulnerability or is obsolete and no longer maintained, the system still schedules a mandatory upgrade for the instance. If you receive such an event notification, you can go to the event center to adjust the upgrade time (recommended) or cancel the upgrade.
Q: Why do different data shard nodes in my cluster instance have different minor versions?
A: For a classic edition cluster, when a data shard node is rebuilt or a switchover occurs, the latest minor version is deployed by default. This can cause version inconsistencies between different data shard nodes but does not lead to compatibility issues. The version displayed in the console or returned by the API is the lowest version among all nodes in the cluster. When you upgrade the minor version or change the instance configuration, the versions of all data shard nodes are aligned.
NoteThe minor versions across all nodes of a cloud-native edition cluster instance are always consistent.
API reference
API | Description |
Queries an instance's major and minor version information and the release notes for the minor version. | |
Upgrades the minor version of an instance. |