Alibaba Cloud releases new 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 release notes for minor versions of ApsaraDB for Redis Community Edition. 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 current minor version of proxy nodes that belong to an instance in the ApsaraDB for Redis console. For more information about update operations and usage notes, 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 is not displayed or is dimmed.
  • 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 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.

V7.0

Minor version Update level Release date Type Description
7.0.0.4 LOW 2022-06-20 Feature optimization
  • New features and enhancements of open source Redis 7.0.2 are supported.
7.0.0.3 LOW 2022-05-27 First release
  • ApsaraDB for Redis Community Edition 7.0 instances that use cloud disks are available. For more information, see Redis 7.0 release notes.

V6.0

Minor version Update level Release date Type Description
0.1.19 LOW 2022-06-22 Feature optimization
  • Latency histograms are optimized. For more information, see Latency insight.
Security hardening
0.1.18 LOW 2022-05-17 Feature optimization
  • The Errorstats – Selected field returned by the INFO command can be deleted.
0.1.17 LOW 2022-05-10 Feature optimization
  • The MOVE command is supported by cluster instances.
0.1.16 MEDIUM 2022-04-25 Security hardening
  • The process of adding and deleting nodes for a cluster instance is optimized to enhance stability.
0.1.15 LOW 2022-03-24 New feature
  • Latency histograms are supported. For more information, see Latency insight.
  • Error statistics can be returned by the INFO command.
0.1.14 LOW 2022-02-21 Feature optimization
0.1.13 LOW 2022-01-14 Feature optimization
  • A metric is added to monitor the amount of memory occupied by database metadata.
  • The real-time key statistics feature is optimized.
0.1.12 HIGH 2021-10-26 Security hardening
  • The following issue is fixed to enhance stability: An excessive number of slow logs are recorded during configuration changes of cluster instances.
0.1.11 HIGH 2021-10-13 Feature optimization
  • The autonomous capabilities to implement imperceptible slot migration during configuration changes of cluster instances are enhanced.
  • The performance of commands such as CLUSTER NODES is optimized.
  • The whitelist feature is optimized.
0.1.10 HIGH 2021-09-06 Feature optimization
  • Stability is enhanced.
0.1.9 MEDIUM 2021-08-16 Feature optimization
  • The reliability of imperceptible slot migration is enhanced to strengthen stability.
0.1.8 MEDIUM 2021-08-06 Feature optimization
  • Stability is enhanced.
0.1.7 MEDIUM 2021-08-06 Feature optimization
  • Stability is enhanced.
0.1.6 MEDIUM 2021-07-19 New feature
  • New features and enhancements of open source Redis 6.0.14 are supported. For more information, see Redis 6.0 release notes.
Feature optimization
  • The process of deleting slots from the source instance after data migration is complete is optimized. This enhances data reliability.
  • The process of migrating incremental data by using slots is simplified.
0.1.5 MEDIUM 2021-06-04 Feature optimization
  • Stability is enhanced.
0.1.4 MEDIUM 2021-05-27 Feature optimization
  • Stability is enhanced.
0.1.3 LOW 2021-05-18 New feature
  • Statistics of large keys can be collected in real time.
0.1.2 MEDIUM 2021-05-07 Feature optimization
  • Stability is enhanced.
0.1.1 MEDIUM 2020-11-28 New feature
  • New features and enhancements of open source Redis 6.0.9 are supported. For more information, see Redis 6.0 release notes.
  • Slots can be migrated without impacting the instance.
  • Virtual IP addresses (VIPs) can be obtained over the Internet. This provides better support for clients that use direct connection mode. For more information, see Enable the direct connection mode.
Feature optimization
  • Health checks for instances are improved to accelerate the switchover between the master and replica nodes when disk jitters occur.
0.0.5 HIGH 2020-08-21 Fixed issue
  • The issue that statistics about hotkeys are inaccurate is fixed.
0.0.4 HIGH 2020-07-20 Fixed issue
  • The issue that the settings of specific parameters become invalid after the instance is restarted is fixed.
  • The issue that replica nodes are incorrectly flagged in slow logs during data synchronization is fixed.
0.0.3 LOW 2020-06-11 New feature
  • New features and enhancements of open source Redis 6.0.5 are supported. For more information, see Redis 6.0 release notes.
  • The role information can be contained in the Replication part of the INFO command output, such as role:master. This allows Redisson clients to call the role information in specific scenarios.
  • Statistics on queries per second (QPS) of read and write commands can be collected. For more information, see View monitoring data.
0.0.2 LOW 2020-06-02 New feature
  • New features and enhancements of open source Redis 6.0.4 are supported. For more information, see Redis 6.0 release notes.
0.0.1 LOW 2020-05-06 First release
  • The first minor version that is available. This minor version is developed based on open source Redis 6.0.1. For more information, see Redis 6.0 release notes.

V5.0

Minor version Update level Release date Type Description
5.1.9 LOW 2022-06-22 Feature optimization
  • Latency histograms are optimized. For more information, see Latency insight.
Security hardening
5.1.8 LOW 2022-05-17 Feature optimization
  • The Errorstats – Selected field returned by the INFO command can be deleted.
5.1.7 LOW 2022-05-06 Feature optimization
  • The MOVE command is supported by cluster instances.
5.1.6 MEDIUM 2022-04-25 Feature optimization
  • The process of adding and deleting nodes for a cluster instance is optimized to enhance stability.
5.1.5 LOW 2022-04-13 Feature optimization
  • Stability is enhanced.
5.1.4 LOW 2022-03-24 New feature
  • Latency histograms are supported. For more information, see Latency insight.
  • Error statistics can be returned by the INFO command.
5.1.3 LOW 2022-02-21 Feature optimization
5.1.1 LOW 2022-01-04 Feature optimization
  • A metric is added to monitor the amount of memory occupied by database metadata.
5.0.9 LOW 2021-12-22 Feature optimization
  • The real-time key statistics feature is optimized.
5.0.8 LOW 2021-11-15 Feature optimization
  • A cluster instance can be scaled without impacting the instance.
0.5.17 HIGH 2022-06-07 Security hardening
  • Stability is enhanced.
0.5.16 HIGH 2022-05-23 Security hardening
  • The configuration change stability is improved for cluster instances that have the direct connection mode enabled.
0.5.15 HIGH 2022-04-25 Security hardening
  • The following issue is fixed: The migration of large keys may fail during configuration changes of cluster instances that have the direct connection mode enabled.
0.5.14 LOW 2022-01-04 Feature optimization
  • A metric is added to monitor the amount of memory occupied by database metadata.
0.5.12 LOW 2021-11-29 Feature optimization
  • The following issue is fixed: Cluster instances may fail to be restarted in specific scenarios.
0.5.11 LOW 2021-11-24 Feature optimization
  • The following issue is fixed: Statistics of SPOP commands are not collected when the real-time key analysis feature is used.
0.5.10 HIGH 2021-10-26 Security hardening
  • The following issue is fixed to enhance stability: An excessive number of slow logs are recorded during configuration changes of cluster instances.
0.5.9 HIGH 2021-10-15 Security hardening
  • Stability is enhanced.
0.5.8 MEDIUM 2021-10-13 Feature update
  • The autonomous capabilities to implement imperceptible slot migration during configuration changes of cluster instances are enhanced.
0.5.7 LOW 2021-08-26 New feature
  • Statistical data of QPS is classified. Three types of QPS can be calculated: read QPS, write QPS, and other QPS.
0.5.6 HIGH 2021-08-16 Fixed issue
  • The reliability of imperceptible slot migration is enhanced to strengthen stability.
0.5.5 HIGH 2021-08-05 Fixed issue
  • The following issue is fixed: Configuration changes may fail when the direct connection mode is enabled for cluster instances.
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 complete is optimized to enhance data reliability.
  • Incremental data synchronization is simplified during data migration.
0.5.2 HIGH 2021-04-26 Security hardening
  • The security vulnerabilities of the open source LuaJIT compiler are fixed.
New feature
  • The migration mechanism for slots is optimized to allow instances that use cloud disks to be scaled without data loss.
  • Statistics of large keys can be collected in real time.
  • VIPs can be obtained over the Internet. This provides better support for private endpoint users.
0.5.0 MEDIUM 2021-03-25 New feature
  • Slots can be migrated without impacting the instance.
Feature optimization
  • The stability is enhanced when a large number of asynchronous client requests are processed.
0.4.0 MEDIUM 2021-03-09 New feature
  • Statistics of large keys can be collected in real time.
  • The CONFIG RESETSTAT command is supported.
  • When the illegal address error message is returned, the IP address of the client can be included in the error message. An IP address whitelist can be configured for your instance based on the IP address prompt.
    Figure 2. IP address prompt
    IP address prompt
Feature optimization
  • Health checks for instances are improved to accelerate the switchover between the master and replica nodes when disk jitters occur.
0.3.10 HIGH 2020-09-25 Fixed issue
  • The issue that the output of the CLUSTER NODES command is inconsistent with that of open source Redis is fixed. Multiple slots are separated by spaces to prevent 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 to simplify O&M. To allow ECS instances to access an ApsaraDB for Redis instance, you can add the security groups to which the ECS instances belong to the ApsaraDB for Redis instance. You do not need to manually add the IP addresses of the ECS instances to the whitelists of the ApsaraDB for Redis instance. 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 issue of expiration times being parsed incorrectly when slots are migrated is fixed.
  • Latency flag bits in audit logs are modified to help you identify these bits in master and replica audit logs.
0.3.7 HIGH 2020-06-17 Fixed issue
  • The issue that the returned IP address cannot be accessed in direct connection mode is fixed.
0.3.6 LOW 2020-06-09 New feature
  • The role information can be contained in the Replication part of the INFO command output, such as role:master. This allows Redisson clients to call the role information in specific scenarios.
0.3.5 LOW 2020-06-05 New feature
  • Statistics on QPS of read and write commands can be collected. For more information, see View monitoring data.
0.3.4 HIGH 2020-04-08 Fixed issue
  • The issue of the system not responding when hotkeys are evicted is fixed.
  • The following issue is fixed: The system does not respond due to the use-after-free (UAF) vulnerability 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 audit log feature.
  • The direct connection mode is supported. Clients can bypass proxy nodes and use private endpoints to connect to ApsaraDB for Redis instances. This is similar to the connection to a native Redis cluster. The direct connection mode can reduce communication overheads and the response time of ApsaraDB for Redis. For more information, see Enable the direct connection mode.
  • Both password-free access and Internet access are supported for an ApsaraDB for Redis instance deployed in a virtual private cloud (VPC). To access the instance from the Internet, apply for a public endpoint. For more information, see Enable password-free access.
  • The oom_err_count information can be contained in the INFO command output when the actual memory size is greater than the value specified for the maxmemory parameter.
Fixed issue
  • The following issue is fixed: The system does not respond because the expiration mechanism is triggered when the RPOPLPUSH command is run with the same source and destination key.
  • The following issue is fixed: Authentication failures occur when 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 earlier minor versions belong to V5.0. We recommend that you update your instances to the latest minor version.

V4.0

Minor version Update level Release date Type Description
1.9.12 HIGH 2022-06-07 Security hardening
  • Stability is enhanced.
1.9.10 HIGH 2022-05-23 Security hardening
  • The configuration change stability is improved for cluster instances that have the direct connection mode enabled.
1.9.9 HIGH 2022-04-25 Security hardening
  • Stability is enhanced.
1.9.8 HIGH 2022-04-25 Security hardening
  • The following issue is fixed: The migration of large keys may fail during configuration changes of cluster instances that have the direct connection mode enabled.
1.9.6 HIGH 2021-10-15 Security hardening
  • Stability is enhanced.
1.9.5 LOW 2021-09-13 New feature
  • Statistical data of QPS is classified. Three types of QPS can be calculated: read QPS, write QPS, and other QPS.
1.9.4 HIGH 2021-08-05 Fixed issue
  • The following issue is fixed: Configuration changes may fail when the direct connection mode is enabled for cluster instances.
1.9.3 MEDIUM 2021-07-20 Feature update
  • Stability is enhanced.
1.9.2 HIGH 2021-04-19 Security hardening
  • The security vulnerabilities of the open source LuaJIT compiler are fixed.
New feature
  • VIPs can be obtained over the Internet. This provides better support for private endpoint users.
1.9.1 MEDIUM 2021-03-08 Feature optimization
  • Health checks for instances are improved to accelerate the switchover between the master and replica nodes when disk jitters occur.
  • The capability of memory-intensive instances to run the BGSAVE and REWRITE commands by calling fork() is improved. This prevents long pauses.
1.9.0 LOW 2021-02-22 New feature
  • When the illegal address error message is returned, the IP address of the client can be included in the error message. An IP address whitelist can be configured for your 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 issue that the output of the CLUSTER NODES command is inconsistent with that of open source Redis is fixed. Multiple slots are separated by spaces to prevent errors in client parsing.
1.8.7 LOW 2020-07-20 New feature
  • The security group feature provided by ECS is supported to simplify O&M. To allow ECS instances to access an ApsaraDB for Redis instance, you can add the security groups to which the ECS instances belong to the ApsaraDB for Redis instance. You do not need to manually add the IP addresses of the ECS instances to the whitelists of the ApsaraDB for Redis instance. For more information, see Step 2: Configure whitelists.
1.8.6 HIGH 2020-07-14 Fixed issue
  • Latency flag bits in audit logs are modified to help you identify these bits in master and replica audit logs.
1.8.5 LOW 2020-06-09 New feature
  • The role information can be contained in the Replication part of the INFO command output, such as role:master. This allows Redisson clients to call the role information in specific scenarios.
1.8.4 LOW 2020-06-05 New feature
  • Statistics on QPS of read and write commands can be collected. For more information, see View monitoring data.
1.8.3 HIGH 2020-04-08 Fixed issue
  • The issue of the system not responding when hotkeys are evicted is fixed.
  • The issue of the system not responding due to the UAF vulnerability is fixed. This issue occurs when the audit log feature is disabled.
1.8.1 LOW 2020-02-20 New feature
  • Both password-free access and Internet access are supported for an ApsaraDB for Redis instance deployed in a VPC. To access the instance from the Internet, apply for a public endpoint. For more information, see Enable password-free access.
1.8.0 HIGH 2020-01-16 New feature
Fixed issue
  • In direct connection mode, the output of the INFO command can contain the cluster_enabled information. This cluster_enabled information allows some SDKs to automatically negotiate 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 proxy nodes and use private endpoints to connect to ApsaraDB for Redis instances. This is similar to the connection to a native Redis cluster. The direct connection mode can reduce communication overheads and the response time of ApsaraDB for Redis. For more information, see Enable the direct connection mode.
  • The memory statistics of Lua scripts can be contained in the Memory part of the INFO command output.
Feature optimization
  • Audit logs consume less memory.
1.5.8 HIGH 2019-09-23 Fixed issue
  • The following issue is fixed: 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
  • The following issue is fixed: Switchover may occur between the master and replica nodes due to slow requests when the client issues commands such as KEYS, FLUSHALL, and FLUSHDB.
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 audit log feature.
  • Latency statistics during the entire event lifecycle are recorded to help you understand the state of the engine.
1.5.2 HIGH 2019-07-04 Fixed issue
  • The following issue is fixed: The system does not respond because the expiration mechanism is triggered when the RPOPLPUSH command is run with the same source and destination key.
1.4.0 HIGH 2019-05-15 Fixed issue
  • The following issue is fixed: Master/replica switchover is triggered when Redis database (RDB) files or append-only files (AOFs) are loaded onto an instance after the instance is restarted.
Earlier than 1.4.0 N/A N/A N/A
  • These earlier minor versions belong to V4.0. We recommend that you update your instances to the latest minor version.