EOFS scheduled for Redis Open-Source Edition 4.0 instances - Tair (Redis® OSS-Compatible)

Starting July 31, 2025, Tair (Redis OSS-compatible) is scheduled to discontinue full support for Redis Open-Source Edition 4.0 instances. At the end of full support (EOFS), we will no longer provide feature updates, security fixes, and technical support for the version. Upgrade your instances to a later version at the earliest opportunity.

Effective from

00:00 on July 31, 2025

Impacts

Existing Redis Open-Source Edition 4.0 instances can still be used, but full support for the instances is coming to an end. This end of support covers the following aspects:

Service purchase is not allowed.
Iterative feature upgrade is not allowed.
Renewal is not allowed.
Configuration change and scaling are not allowed.
After-sales service is unavailable.
New patch releases and bug fixes are no longer provided.

Suggestions

Upgrade the major version: We recommend that you upgrade your instances to 5.0. Redis Open-Source Edition 5.0 is fully backward compatible with the commands from Redis Open-Source Edition 4.0. In addition, Redis Open-Source Edition 5.0 has made significant improvements in key areas such as master-replica replication and persistence mechanisms, and introduces more new features.
Upgrade task execution process in the background:
1. The replica node is upgraded first. During this phase, the master node remains fully operational with support for normal read and write operations.
2. After the upgrade is complete, a master-replica switchover is performed. The master-replica switchover time is determined based on your specifications at the time of initiating the upgrade. You can choose to perform the switchover immediately or schedule the switchover to occur during the specified maintenance window. 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.
  Note
  After the upgrade is complete, the configurations of the original instance, such as the instance ID, endpoints, data, whitelists, accounts, and account passwords, remain unchanged.
Clone data to a Redis Open-Source Edition 5.0 instance: If you want to verify the upgrade against your current business logic in Redis Open-Source Edition 5.0, you can clone a new instance first.
Change the configurations of an instance: You can use the configuration change feature to change your instance into a Redis Open-Source Edition 5.0 instance or a Tair (Enterprise Edition) instance.

FAQ

Do I need to upgrade an existing Redis Open-Source Edition 4.0 instance to a later version?

It is not mandatory to upgrade a Redis Open-Source Edition 4.0 instance to a later version. However, we recommend that you perform the upgrade.

What commands do later versions of Redis Open-Source Edition support?

Extensive compatibility regression testing is performed on the data structures and APIs of later versions of Redis Open-Source Edition. For more information, see Commands supported by Redis Open-Source Edition.

How do I test the compatibility before an upgrade?

You can restore the backup data of a Redis Open-Source Edition 4.0 instance to a new Redis Open-Source Edition 5.0 instance.

When you configure the new instance, select Redis 5.0 as the major version for the new instance. Then, select the pay-as-you-go billing method to conduct testing and verification at a lower cost. After you complete verification, you can release the instance to conserve resources.

Tair (Redis® OSS-Compatible):[Notice] EOFS scheduled for Redis Open-Source Edition 4.0 instances