Upgrading to a newer major version gives your instance higher performance, better security, and access to new features — without creating a new instance. Your instance ID, endpoints, data, whitelist configurations, and accounts remain unchanged after the upgrade.
A major version upgrade cannot be reversed. To revert to an earlier version, create a new instance of the earlier version and migrate your data to it.
Eligibility
Not all instances support a major version upgrade. Review the table below before proceeding.
| Condition | Supported | Action required |
|---|---|---|
| Instances in different deployment modes | No | You can only upgrade within the same deployment mode. |
| Classic network instance | Partially | Maximum target version is 5.0. To reach 6.0 or later, first convert to cloud-native. |
| Cloud-native instance (cluster architecture, direct connection mode) | No | Major version upgrade is not supported for this configuration. |
| Instance with active Data Transmission Service (DTS) tasks | No | Pause all DTS tasks first, then retry. |
| Classic cluster instance with a private endpoint | No | Release the private endpoint first, then retry. |
| Instance connected to the classic network | No | Release the classic network connection first. It cannot be re-established after release. Use a Virtual Private Cloud (VPC) instead — it is faster and more secure. |
| Memory usage above 80% | Not recommended | A major version upgrade can change memory usage by approximately −10% to 10%. Keep memory usage below 80% before upgrading to avoid running out of memory afterward. |
| Redis Open-Source Edition 2.8 instance | Partially | Can only be upgraded to version 5.0. |
| Retired instance type | No | Change the instance configuration to an available type with the same memory capacity first, then retry. |
Upgrade impact
Pre-upgrade tasks — resource provisioning, secondary database upgrades, and data synchronization — run in the background without affecting your instance.
The impact window occurs only during the instance switchover or a primary/secondary failover:
The instance becomes read-only for up to 60 seconds while data is synchronized.
A transient connection lasting a few seconds occurs.
To minimize disruption, schedule the upgrade during off-peak hours or use the Update During Maintenance option to let the system perform the switchover during your configured maintenance window.
Bloom filter API compatibility (Redis Open-Source Edition 4.0 only)
If your application uses Bloom filter APIs such as BF.ADD, these APIs are not supported after a major version upgrade. The Bloom filter operations in early Redis 4.0 instances were not officially released for public use and are no longer available in later major versions or in newly created Redis 4.0 instances. Continuing to use them poses unknown risks, including cache analysis failures.
Switch to a Tair memory-optimized instance to use its optimized Bloom filters.
Upgrade the major version in the console
Make sure your application has a reconnection mechanism configured before you start the upgrade.
Log on to the console and go to the Instances page. In the top navigation bar, select the region where your instance is deployed. Find the instance and click its ID.
In the Configuration Information section, find the Version field and choose Update > Major Update.
NoteIf the Major Update option is unavailable, the instance is not eligible for a major version upgrade.
In the panel that opens, select the target version and the execution time. To minimize the impact of the switchover, select Update During Maintenance. The system then performs the switchover during the instance's maintenance window. For details, see Set a maintenance window.
Click OK.
FAQ
Why did the upgrade fail?
The upgrade fails if the instance is a retired instance type. Change the instance configuration to an available type with the same memory capacity, then retry the major version upgrade.
The instance status changed to "Upgrading" immediately after I selected Update During Maintenance. Is something wrong?
No. The system is running pre-upgrade tasks such as resource provisioning and data synchronization. These tasks do not involve an instance switchover or primary/secondary failover and have no impact on your instance's services. The read-only period and transient connection occur only during the switchover itself.
Is a major version upgrade free?
Yes. Major version upgrades are free of charge.
Can I downgrade after upgrading?
No. To run an earlier version, create a new instance of that version and migrate your data to it.
Which version can a Redis Open-Source Edition 2.8 instance be upgraded to?
A Redis Open-Source Edition 2.8 instance can only be upgraded to version 5.0.
How do I upgrade a classic 5.0 instance to 6.0?
Convert the classic instance to a cloud-native instance and select Redis 6.0 or a later version during the conversion.