Alibaba Cloud releases minor versions of ApsaraDB for Redis from time to time to provide more features, fix known issues, and improve user experience. This topic describes the minor version updates of ApsaraDB for Redis Community Edition (Tair). We recommend that you update minor versions of instances during off-peak hours.

View or update the minor version of an instance

You can view the minor version of the current instance in the console. For more information about how to view and update the minor version of an instance, see Update the minor version.

Figure 1. View the minor version
View the minor version
Notice
  • The system automatically detects the minor version of an instance. If the instance is of the latest minor version, the Minor Version Upgrade button does not exist or cannot be clicked.
  • Minor version updates may differ from region to region. The minor version of an instance displayed in the ApsaraDB for Redis console prevails.

Update levels

  • LOW: regular update. This level includes routine feature updates, such as adding a feature.
  • MEDIUM: recommended update. This level includes optimization of features and modules, such as optimizing a feature. Moreover, LOW-level updates are included in this level.
  • HIGH: important update. This level includes major updates that ensure stability or security, such as fixing a vulnerability or defect. Moreover, LOW-level and MEDIUM-level updates are included in this level.

V5.0

Minor version number Update level Release date Type Description
0.5.4 MEDIUM 2021-07-27 Feature update
  • Stability is enhanced.
0.5.3 MEDIUM 2021-07-21 Feature update
  • The process of deleting source data after data migration is optimized to enhance data reliability.
  • Incremental data synchronization is simplified for data migration.
0.5.2 HIGH 2021-04-26 Security hardening
  • The vulnerability of LuaJIT is fixed.
New feature
  • The migration mechanism for slots is optimized to allow instances that are equipped with disks to be scaled without data loss on the disks.
  • The number of big keys can be calculated in real time.
  • Virtual IP addresses (VIPs) can be obtained over the Internet. This provides better support for users in direct connection mode.
0.5.0 MEDIUM 2021-03-25 New feature
  • Slots can be migrated without perceptible impacts on your business.
Feature optimization
  • Stability is improved when a large number of asynchronous client requests are processed.
0.4.0 MEDIUM 2021-03-09 New feature
  • The number of big keys can be calculated in real time.
  • The CONFIG RESETSTAT command is supported.
  • The IP address of the client is included when an illegal address error message is returned. An IP address whitelist can be configured for your ApsaraDB for Redis instance based on the IP address prompt.
    Figure 2. IP address prompt
    IP address prompt
Feature optimization
  • Health checks for ApsaraDB for Redis instances are improved to accelerate the switchover between the master and replica nodes when disk jitter occurs.
0.3.10 HIGH 2020-09-25 Fixed issue
  • The output of the CLUSTER NODES command is inconsistent with that of open source protocols. This issue is fixed by separating multiple slots with spaces to avoid errors in client parsing.
0.3.9 LOW 2020-07-20 New feature
  • The security group feature provided by Elastic Compute Service (ECS) is supported. You can grant permissions to ApsaraDB for Redis instances when you add the ApsaraDB for Redis instances to security groups to which ECS instances belong. You do not need to manually enter the IP addresses of the ECS instances. This simplifies O&M. For more information, see Step 2: Configure whitelists.
0.3.8 HIGH 2020-07-14 Feature optimization
  • Subcommands of CLIENT UNBLOCK are available.
Fixed issue
  • The expiration time is not correctly parsed when slots are migrated.
  • Latency flag bits are difficult to identify in master and replica audit logs.
0.3.7 HIGH 2020-06-17 Fixed issue
  • The returned IP address cannot be accessed in direct connection mode.
0.3.6 LOW 2020-06-09 New feature
  • The Replication part of the INFO command output shows the role information, such as role:master. This allows Redisson clients to call the role information in some scenarios.
0.3.5 LOW 2020-06-05 New feature
  • Statistics for queries per second (QPS) of read and write commands can be collected. For more information, see Query monitoring data.
0.3.4 HIGH 2020-04-08 Fixed issue
  • The system may not respond when hotkeys are evicted.
  • The system may not respond due to use-after-free (UAF) when the audit log feature is disabled.
0.3.1 HIGH 2020-02-20 New feature
  • The audit log feature is supported. This feature allows you to query, analyze online, and export logs. For more information, see Enable the new version of the audit log feature.
  • The direct connection mode is supported. Clients can bypass proxies to connect to ApsaraDB for Redis instances by using direct connection endpoints. The direct connection mode can reduce link overheads and further improve the response speed of ApsaraDB for Redis. For more information, see Enable the direct connection mode.
  • You can apply for public endpoints when you want to access ApsaraDB for Redis instances that are deployed in virtual private clouds (VPCs) without using passwords. For more information, see Enable password-free access.
  • The output of the INFO command contains the oom_err_count information when the actual memory size is greater than the value specified for the maxmemory parameter.
Fixed issue
  • The system does not respond because the expiration mechanism is triggered when the RPOPLPUSH command is run. For the RPOPLPUSH command, the source and destination parameters are identical.
  • Authentication failure occurs when ApsaraDB for Redis instances that are deployed in VPCs are accessed without using passwords.
0.2.0 LOW 2020-01-17 New feature
0.1.2 LOW 2019-11-26 New feature
Earlier than 0.1.2 N/A N/A N/A
  • These minor versions belong to 5.0. We recommend that you update them to the latest minor version.

V4.0

Minor version number Update level Release date Type Description
1.9.3 MEDIUM 2021-07-20 Feature update
  • Stability is enhanced.
1.9.2 HIGH 2021-04-19 Security hardening
  • The vulnerability of LuaJIT is fixed.
New feature
  • VIPs can be obtained over the Internet. This provides better support for users in direct connection mode.
1.9.1 MEDIUM 2021-03-08 Feature optimization
  • Health checks for ApsaraDB for Redis instances are improved to accelerate the switchover between the master and replica nodes when disk jitter occurs.
  • The capability of memory-intensive instances to run the BGSAVE and REWRITE commands by calling fork() is improved to prevent long pauses.
1.9.0 LOW 2021-02-22 New feature
  • The IP address of the client is included when an illegal address error message is returned. An IP address whitelist can be configured for your ApsaraDB for Redis instance based on the IP address prompt.
    Figure 3. IP address prompt
    IP address prompt
1.8.8 HIGH 2020-09-25 Fixed issue
  • The output of the CLUSTER NODES command is inconsistent with that of open source protocols. This issue is fixed by separating multiple slots with spaces to avoid errors in client parsing.
1.8.7 LOW 2020-07-20 New feature
  • The security group feature provided by ECS is supported. You can grant permissions to ApsaraDB for Redis instances when you add the ApsaraDB for Redis instances to security groups to which ECS instances belong. You do not need to manually enter the IP addresses of the ECS instances. This simplifies O&M. For more information, see Step 2: Configure whitelists.
1.8.6 HIGH 2020-07-14 Fixed issue
  • Latency flag bits are difficult to identify in master and replica audit logs.
1.8.5 LOW 2020-06-09 New feature
  • The Replication part of the INFO command output shows the role information, such as role:master. This allows Redisson clients to call the role information in some scenarios.
1.8.4 LOW 2020-06-05 New feature
  • Statistics for QPS of read and write commands can be collected. For more information, see Query monitoring data.
1.8.3 HIGH 2020-04-08 Fixed issue
  • The system may not respond when hotkeys are evicted.
  • The system may not respond due to UAF when the audit log feature is disabled.
1.8.1 LOW 2020-02-20 New feature
  • You can apply for public endpoints when you want to access ApsaraDB for Redis instances that are deployed in VPCs without using passwords. For more information, see Enable password-free access.
1.8.0 HIGH 2020-01-16 New feature
Fixed issue
  • The output of the INFO command does not contain the cluster_enabled information in the direct connection mode, which prevents some SDKs from automatically negotiating to enter the cluster mode. For more information, see Enable the direct connection mode.
1.7.1 MEDIUM 2019-11-20 New feature
  • Read-only Lua scripts can be executed on read replicas of read/write splitting instances.
  • The direct connection mode is supported. Clients can bypass proxies to connect to ApsaraDB for Redis instances by using direct connection endpoints in the same manner as they connect to native Redis clusters. The direct connection mode can reduce link overheads and further improve the response speed of ApsaraDB for Redis. For more information, see Enable the direct connection mode.
  • In the output of the INFO command, the memory information of the Lua script is added to the Memory value.
Feature optimization
  • Audit logs consume less memory.
1.5.8 HIGH 2019-09-23 Fixed issue
  • The atomicity of the SETEX command is destroyed during two-way synchronization in Global Distributed Cache for Redis links.
1.5.6 HIGH 2019-08-28 New feature
  • Audit logs can record latency events.
Fixed issue
  • Switchovers may occur between master and replica nodes when the commands such as KEYS, FLUSHALL, and FLUSHDB initiated by the client are slow to run.
1.5.4 LOW 2019-07-08 New feature
  • The audit log feature is supported. This feature allows you to query, analyze online, and export logs. For more information, see Enable the new version of the audit log feature.
  • Latency during the entire event lifecycle is recorded to help you understand the status of the engine.
1.5.2 HIGH 2019-07-04 Fixed issue
  • The system does not respond because the expiration mechanism is triggered when the RPOPLPUSH command is run. For the RPOPLPUSH command, the source and destination parameters are identical.
1.4.0 HIGH 2019-05-15 Fixed issue
  • Switchover is triggered between the master and replica nodes when files in the Redis Database (RDB) or append-only file (AOF) format are loaded to an ApsaraDB for Redis instance after the instance is restarted.
Earlier than 1.4.0 N/A N/A N/A
  • These minor versions belong to 4.0. We recommend that you update them to the latest minor version.