Tair (Redis® OSS-Compatible):[Notice] End-of-life plan for Redis Open-Source Edition 2.8 instances

Involved version

Redis Open-Source Edition 2.8

End-of-life plan

• End of Full Support (EOFS) date: February 4, 2025 (UTC+8)

• End of Service (EOS) date: August 4, 2025 (UTC+8)

Impacts

• Starting from the EOFS date, existing subscription instances that run Redis 2.8 can no longer be renewed, and no new features or feature updates will be provided for the instances.

  Existing pay-as-you-go instances that run Redis 2.8 can continue to function normally until the end of their lifecycle, which is defined as the EOS date.

• Starting from the EOS date, all services and support related to existing instances that run Redis 2.8 will be discontinued. This includes, but is not limited to, instance access, documentation, security patches, bug fixes, and after-sales service.

Suggestions

• Upgrade the major version: As Tair 4.0 is also approaching the end of its lifecycle, we recommend that you upgrade instances that run Redis 4.0 to run Tair 5.0. Tair 5.0 is fully backward compatible with the commands from Tair 2.8 and Tair 4.0. In addition, Redis 5.0 has made significant improvements in key areas such as master-replica replication and persistence mechanisms, and introduces more new features.

  Upgrading the major version of an instance typically does not result in data loss and usually has minimal impact on the business. However, we recommend that you upgrade your instances during off-peak hours. The upgrade process of an instance entails the following steps:

  1. Upgrade the replica node first. During this phase, the master node remains fully operational with support for normal read and write operations.

  2. After the replica node is upgraded, perform a master-replica switchover. 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 from an instance that runs Redis 2.8 to an instance that runs Redis 5.0: If you want to validate the upgrade against your current business logic in Tair 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 an instance that runs Tair 5.0 or an ApsaraDB for Redis Enhanced Edition (Tair) instance.

For more information, see Lifecycle policy. If you have any questions, submit a ticket.