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 minor version updates of ApsaraDB for Redis Enhanced 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.

Introduction to ApsaraDB for Redis Enhanced Edition (Tair)

The rapid development of the Internet makes business scenarios become more diverse and complicated. ApsaraDB for Redis Enhanced Edition (Tair) is a high-availability and high-performance NoSQL database service. It provides various series of instances based on storage media such as DRAM, NVM, and ESSDs to meet your requirements for low-latency access, persistence, and reduced overall cost. Tair provides you with higher performance, more data structures, and more flexible storage methods. This helps you meet business requirements in different scenarios.

Type Feature
Performance-enhanced instances
Persistent memory-optimized instances Persistent memory-optimized instances adopt Intel® Optane™ DC persistent memory (AEP) to provide you with in-memory databases that have a large capacity and are compatible with open source Redis. A persistent memory-optimized instance does not use disks to implement data persistence. It saves up to 30% of costs compared with an ApsaraDB for Redis Community Edition instance and provides almost the same performance in terms of throughput and latency. This helps improve the reliability of business data.
Storage-optimized instances Storage-optimized instances are developed based on ESSDs and compatible with core data structures and interfaces of open source Redis. These instances can provide large-capacity, low-cost, and persistent database services. Storage-optimized instances reduce costs and improve data reliability. In addition, storage-optimized instances reduce the amount of reserved memory that is required for the forks of native Redis databases. This instance type applies to scenarios that store warm and cold data, and require compatibility with Redis, large capacity, and high access performance.
Hybrid-storage instances Hybrid-storage instances store data in both memory and disks. During off-peak hours, hybrid-storage instances can separate hot data from cold data to ensure a high memory access speed. Hybrid-storage instances also provide a larger storage capacity than instances of ApsaraDB for Redis Community Edition to balance performance and cost.

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.

Performance-enhanced instances of ApsaraDB for Redis Enhanced Edition (Tair)

Minor version number Update level Release date Type Description
1.7.2 MEDIUM 2021-07-27 Feature optimization
  • Stability is enhanced.
1.7.1 MEDIUM 2021-07-20
Note The minor version is gradually released in various regions.
New feature
  • Transparent Data Encryption (TDE) can be used to perform encryption and decryption on data files of Redis Database (RDB). For more information, see Enable TDE.
Feature optimization
  • The memory usage of the TairHash data structure is optimized.
1.6.15 MEDIUM 2021-07-12 Feature optimization
  • Stability is enhanced.
1.6.9 LOW 2021-06-22 New feature
  • Latency histograms are supported.
1.6.6 MEDIUM 2021-06-08 Feature optimization
  • Stability is enhanced.
1.6.3 LOW 2021-05-17 New feature
  • Some functions of keys are retained based on keys or key patterns when data is cleared. This feature can be used in the following scenarios:
    • Restore some keys or key patterns when you use the data flashback feature to restore data to a point in time. For more information, see Use data flashback to restore data by point in time.
    • Delete or retain the keyspace content based on keys or key patterns.
1.6.2 MEDIUM 2021-04-25 Feature optimization
  • The performance and migration speed during imperceptible scaling operations are optimized.
  • Virtual IP addresses (VIPs) can be obtained over the Internet. This provides better support for clients in direct connection mode. For more information, see Enable the direct connection mode.
  • The big key pattern is optimized.
1.6.1 MEDIUM 2021-04-08 New feature
  • By default, the statistics feature is enabled for big keys.
  • TairString commands support the gt version parameter.
Feature optimization
  • The abilities to migrate slots and implement imperceptible scaling are improved.
1.5.1 HIGH 2021-03-15 Fixed issue
  • When keys of the same name are written, the real-time statistics for big keys are inaccurate.
1.5.0 MEDIUM 2021-02-22 New feature
  • The number of big keys can be calculated in real time.
Feature optimization
  • The liveness detection capability of high-availability (HA) systems is improved when you call fork() in memory-intensive scenarios. This prevents long pauses that may occur.
1.4.16 HIGH 2021-01-11 New feature
Fixed issue
  • Memory leaks occur when the FLUSHALL command is frequently run in TairHash scenarios.
1.4.13 LOW 2020-11-27 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 2. IP address prompt
    IP address prompt
1.4.12 MEDIUM 2020-11-26 New feature
  • Flags such as FLAGS are used in the syntax of TairString commands. This syntax is compatible with memcached semantics.
Feature optimization
  • The liveness detection capability of HA systems is enhanced.
    Note We recommend that you update the minor version to 1.5.0 or later to obtain the latest optimization for this feature.
1.4.9 HIGH 2020-10-22 Fixed issue
  • Incorrect binlogs are generated when TairString commands expire, which results in data inconsistency in the master and replica nodes.
  • Abnormal switchover of HA systems occurs when TairHash commands still use the active expire algorithm in read-only scenarios.
  • The system may not respond when an instance is restarted after it is forcibly stopped.
  • Expired keys are deleted when RDB files are loaded to ApsaraDB for Redis instances and point-in-time data restoration by using the data flashback feature is enabled. For more information, see Use data flashback to restore data by point in time.
1.4.8 HIGH 2020-10-14 Fixed issue
  • Memory leaks may occur when some modules are loaded.
1.4.7 MEDIUM 2020-10-12 Feature optimization
  • The output of the CLUSTER NODES command is stored in the cache. This optimizes the command execution speed.
1.4.6 MEDIUM 2020-09-28 Feature optimization
  • The processing capabilities of some modules in special scenarios are improved.
1.4.1 MEDIUM 2020-09-08 New feature
  • Proxy servers can pass client IP addresses through to operational logs and audit logs. This helps you interpret logs and identify clients that have issues.
Feature optimization
  • The data collection capability is improved. This minimizes the impact on data shards when a large number of connections are queued up and I/O threads are busy.
1.3.17 MEDIUM 2020-08-04 Feature optimization
1.3.16 HIGH 2020-07-19 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.
  • The TairString module is updated to support more API operations (flags) that are compatible with memcached semantics.
Fixed issue
1.3.9 MEDIUM 2020-06-19 Feature optimization
1.3.7 LOW 2020-05-19 New feature
  • The Replication part of the output of the INFO command shows the role information, such as role:master. This allows Redisson clients to call the role information in some scenarios.
1.3.6 MEDIUM 2020-05-19 New feature
  • Hotkeys are shown in logs.
  • The data statistics feature is supported for performance metrics. This feature allows the system to differentiate the queries per second (QPS) that are generated in read, write, and read/write synchronization operations. This improves the accuracy of the statistics.
Feature optimization
  • The kernel capabilities for restoring data to a point in time are improved. This simplifies the data restoration process. For more information, see Use data flashback to restore data by point in time.
  • Commands such as AUTH, ADMINAUTH, and CONFIG are used. These commands do not record sensitive information, which improves data security.
1.3.5 HIGH 2020-04-22 Fixed issue
  • Deadlocks may occur when multi-threaded engines asynchronously disable client connections.
  • File descriptors in engines cannot linearly expand.
1.3.3 HIGH 2020-04-22 New feature
  • The 64-bit Hash algorithm is applied to TairBloom commands.
  • The final memory usage of TairBloom commands can be estimated. This allows the system to record more accurate memory statistics.
  • The exhgetAll2 interface is used in TairHash commands to revise the formats of command outputs.
Fixed issue
  • When a whitelist is not correctly configured, an error message of (error) ERR invalid password is returned by ApsaraDB for Redis. The message changes to (error) ERR illegal address when this issue is fixed.
  • Memory leaks may occur when you use TairGIS commands to manage multiple polygons.
  • The default path for TairDoc commands is incorrect.
  • Pub and Sub commands may compete in multi-threaded engines.
1.3.1 HIGH 2020-04-03 New feature
  • The data flashback feature is supported. This feature allows you to restore instance data to a point in time within the last seven days. This helps prevent data loss caused by improper operations, simplify O&M, and protect databases in real time. For more information, see Use data flashback to restore data by point in time.
  • TairGIS commands are compatible with Redis GEO commands.
  • TairBloom commands can be used in the capacity security validation for the BFRESERVE interface.
  • TairHash commands support the following new features:
    • The NOACTIVE option is added to multiple commands including EXHSET, EXHEXPIRE, EXHINCRBY, and EXHINCRBYFLOAT. This option can reduce memory overheads in some scenarios.
    • The MAX and MIN options are added to the EXHINCRBY command to ensure the value range.
    • The noexp option is added to the EXHLEN command to return the true length of the EXHLEN command.
  • The HINCRBY and HINCRBYFLOAT commands in the hash structure are supported. Transaction processing can be used on the commands to increase and decrease different fields under a key at the same time.
Feature optimization
  • Data structure modules are improved. For more information, see Integration with multiple Redis modules.
  • The JedisCluster client can run the MGET and MSET commands with much higher performance in cluster instances.
Fixed issue
  • Binlog overflows occur.
  • The system may not respond when hotkeys are evicted.
  • The system may not respond due to double deallocation in TairHash commands.
  • The system may not respond due to use-after-free (UAF) when the audit log feature is disabled.
1.0.10 LOW 2020-02-19 New feature
  • The BITFIELD_RO command is used, which significantly optimizes the performance of BITFIELD commands in read/write splitting scenarios.
    Note If BITFIELD commands contain only the get option, proxy servers convert the commands to BITFIELD_RO commands and forward the new commands to multiple backend data shards.
1.0.9 HIGH 2020-02-19 Fixed issue
  • The replication process stops when some complex commands in Lua scripts are run.
1.0.8 HIGH 2020-02-10 Feature optimization
  • The algorithm and performance related to traffic throttling are improved.
Fixed issue
  • Services stop because the congestion of client output buffers triggers server overload protection.
1.0.5 HIGH 2020-02-01 New feature
  • Global Distributed Cache for Redis is supported. This feature is an active geo-redundancy database system that is developed based on ApsaraDB for Redis. Global Distributed Cache for Redis supports business scenarios in which multiple sites in different regions provide services at the same time. Global Distributed Cache for Redis helps enterprises replicate the active geo-redundancy architecture of Alibaba Cloud. For more information, see Overview.
  • Binlogs and their protocols are available to support capabilities such as active geo-redundancy.
Fixed issue
  • The output of the INFO command can contain the cluster_enabled information in the direct connection mode. This cluster_enabled information allows some SDKs to automatically negotiate to enter the cluster mode. For more information, see Enable the direct connection mode.
  • The number of controlled clients is not accurately calculated.
  • The system may not respond when a client is released.
  • The system may not respond when a pipeline contains complex commands.
0.2.9 HIGH 2020-01-06 Feature optimization
Fixed issue
  • The system may not respond when traffic throttling is implemented.
0.2.7 HIGH 2019-12-23 New 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.
  • The identification logic for hotkeys is supported. This allows hotkeys of engines to be accurately found. The memory usage of hotkeys is also optimized.
  • EXCAS commands are supported in optimistic locking scenarios. For more information about how to use EXCAS commands, see EXCAS and Reduce resource consumption for optimistic locking.
Fixed issue
  • The coredump issue may occur when pipelines are used.
0.2.3 LOW 2019-12-03 First release Performance-enhanced instances of ApsaraDB for Redis Enhanced Edition (Tair) are suitable for business scenarios that involve high concurrency, a large number of read and write hotspots, and stringent performance requirements. Compared with ApsaraDB for Redis Community Edition (Tair) instances, performance-enhanced instances have the following advantages:

Persistent memory-optimized instances of ApsaraDB for Redis Enhanced Edition (Tair)

Minor version number Update level Release date Type Description
1.1.7 LOW 2021-08-02 New feature
  • Semi-synchronous data replication is supported. By default, this feature is disabled. If you want to enable this feature, you can submit a ticket.
    Note If this feature is enabled, logs are transmitted from a master node to a replica node after the client data on the master node is upgraded. After the replica node receives all logs, the master node returns the log transmission information to the client. If a replica node is unavailable or a network exception occurs between a master node and a replica node, semi-synchronous replication degrades to the asynchronous mode.
  • In the output of the INFO command, the return value of the redis_version parameter is changed to 4.9.9 and the pena_version parameter is added to indicate the minor version.
1.1.6.1 MEDIUM 2021-06-10 Feature update
  • Stability is enhanced.
1.1.6 MEDIUM 2021-05-08 New feature
  • Imperceptible scaling operations are supported, which allows slots to be migrated without perceptible impacts on your business.
Feature optimization
  • Hash and ZSET data structures support ziplist encoding to reduce memory overheads.
  • The liveness detection capability of HA systems is enhanced.
  • Data migration of large clusters is optimized. Large clusters indicate clusters that have a large number of shards.
  • Scaling stability of the cluster architecture is improved.
1.1.5 MEDIUM 2021-01-15 New feature
  • Cluster master-replica instances are supported. This eliminates the performance bottleneck that is caused by a single-threading model. You can use the high-performance cluster instances to process large-capacity workloads.
  • The minor version of an instance is used as the value of the redis_version parameter in the output of the INFO command.
Feature optimization
  • Service stability is enhanced.
1.1.4 MEDIUM 2020-10-28 New feature
  • When you run the INFO command by using a standard account, the usage of persistent memory is included in the command output.
Feature optimization
  • The space occupied by embstr encoding is decreased to reduce memory overheads.
  • Service stability is enhanced.
1.1.3 LOW 2020-09-16 First release

Persistent memory-optimized instances of ApsaraDB for Redis Enhanced Edition (Tair) are equipped with the Intel® Optane™ DC Persistent Memory Module (AEP) to provide in-memory databases that have a large capacity and are compatible with open source Redis. This type of instances has the following benefits:

  • A persistent memory-optimized instance costs about 30% lower than an ApsaraDB for Redis Community Edition (Tair) instance.
  • In scenarios where advanced memory specifications are used, the issues of latency jitter and slow service data loading during fork operations triggered by append-only file (AOF) rewrites are resolved. You do not need to choose between performance and persistence.
  • Persistent memory-optimized instances support command-level persistence. A response is returned after data persistence is complete for each write operation.
  • Persistent memory-optimized instances are compatible with most of the data structures and interfaces of native Redis. The persistence of data structures except for Redis Streams is supported.
    Note For more information about command limits, see Limits on commands supported by ApsaraDB for Redis Enhanced Edition (Tair).

Storage-optimized instances of ApsaraDB for Redis Enhanced Edition (Tair)

Minor version number Update level Release date Type Description
2.1.5 HIGH 2021-07-13 Fixed issue
  • Binlogs occupy a large amount of space.
2.1.4 MEDIUM 2021-07-07 Feature optimization
  • The storage parameters of storage-optimized instances with terabytes of capacity are optimized to improve performance.
  • Stability is enhanced.
2.1.0 LOW 2021-05-26 New feature
  • The MULTI and EXEC transaction commands are supported.
  • The EVAL, EVALSHA, and SCRIPT Lua script commands are supported.
2.0.13 LOW 2021-04-24 New feature
  • Notifications about keyspace events can be sent.
1.2.17 HIGH 2021-02-04 Fixed issue
  • In extreme cases, the FLUSHALL command may cause data inconsistency in master and replica nodes. This issue is fixed to protect data consistency in master and replica nodes.
1.2.16 HIGH 2021-01-29 Fixed issue
  • In extreme cases, after a master node is disconnected from a replica node, they cannot be automatically reconnected. This issue is fixed to protect data consistency in master and replica nodes.
1.2.15 MEDIUM 2021-01-20 New feature
  • The cmd_slowlog_count metric is added to collect historical statistics of slow logs.
Feature optimization
  • Protection capabilities are improved in scenarios where disk space is fully occupied.
1.2.14 LOW 2020-12-31 New feature
  • Data check for master and replica nodes is added.
1.2.13 HIGH 2020-12-31 Fixed issue
  • Defects are found in some scenarios when the RESTORE command is run.
1.2.12 MEDIUM 2020-12-23 Feature optimization
  • The mechanism to run the FLUSHALL and FLUSHDB commands is optimized, and they cannot be run at the same time.
1.2.11 MEDIUM 2020-12-10 Feature optimization
  • Memory management is optimized.
1.2.10 LOW 2020-12-04 New feature
  • You can access ApsaraDB for Redis instances that are deployed in VPCs without using passwords. For more information, see Enable password-free access.
  • The size of a single transaction is limited by using the max-write-batch-size option to avoid memory overflows caused by large transactions.
1.2.9 MEDIUM 2020-11-27 Feature optimization
  • To make the Redis-shake tool available for data migration scenarios, the value of the redis_version parameter is added to the output of the INFO command.
1.2.8 HIGH 2020-11-20 Fixed issue
  • The number of connections is incorrectly calculated.
  • The number of keys is incorrectly calculated when the RESTORE command is run.
1.2.7 HIGH 2020-10-28 Fixed issue
  • The system exceptionally exits when the SETRANGE command is run.
  • Exceptions occur when keys are empty strings.
1.2.6 HIGH 2020-09-28 Fixed issue
  • A sharp increase in connection management logs occurs.
1.2.5 HIGH 2020-09-27 Fixed issue
  • A sharp increase in operational logs occurs.
1.2.4 HIGH 2020-09-27 Feature optimization
  • The stability of data synchronization between master and replica nodes is improved.
  • The performance of scanning data with complex data structures is optimized.
Fixed issue
  • The ZADD and ZINCR commands are inconsistent with those of native Redis. Semantic errors occur when multiple duplicate members are managed.
  • nil is returned for empty strings when the MGET command is run.
1.2.3 LOW 2020-09-27 First release Storage-optimized instances of ApsaraDB for Redis Enhanced Edition (Tair) are independently developed based on the TairDB key-value storage engine and use enhanced SSDs (ESSDs) to store data. This type of instances provides high-capacity, low-cost, and persistent database services. This type of instances has the following benefits:
  • Storage-optimized instances store data in disks to implement data persistence at a cost that can be as low as 15% that of ApsaraDB for Redis Community Edition (Tair) instances.
  • Storage-optimized instances use multiple I/O threads and worker nodes to improve throughput on each server and support replication of binlogs between master and replica nodes.
  • Storage-optimized instances are compatible with most of the native Redis commands.
  • Storage-optimized instances reduce the amount of reserved memory that is required for the forks of native Redis databases.