Alibaba Cloud releases minor versions of ApsaraDB for Redis from time to time to implement new features, fix known issues, and improve user experience. This topic describes the release notes for minor versions 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 current minor version of 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
Important
  • 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.

ApsaraDB for Redis Enhanced Edition (Tair)

The rapid development of the Internet makes business scenarios more diverse and complicated. ApsaraDB for Redis Enhanced Edition (Tair) is a high-availability and high-performance NoSQL database service. It provides several series of instances based on storage media such as dynamic random-access memory (DRAM), non-volatile memory (NVM), and ESSDs to meet your requirements for low-latency access, persistence, and reduced overall costs. Tair provides higher performance, more data structures, and more flexible storage methods to meet your requirements in a variety of scenarios. For more information about ESSDs, see ESSDs.

Tair instance series are compatible with multiple open source Redis versions.
SeriesDescription
DRAM-based instances
Persistent memory-optimized instances
  • Persistent memory-optimized instances provide ultra-high cost-effectiveness. The price of persistent memory-optimized instances is 30% lower than that of ApsaraDB for Redis Community Edition instances with the same capacity. The performance of persistent memory-optimized instances reaches 90% of that of native Redis databases.
  • Persistent memory-optimized instances support the TairString (including CAS and CAD commands), TairHash, and TairCpc enhanced data structure modules.
  • Persistent memory-optimized instances prevent data loss when power failures occur. These instances implement persistence for each command. The system will return a success response for each write operation only after the data is persistently stored. You can use persistent memory-optimized instances as in-memory databases instead of caches.
  • Persistent memory-optimized instances optimize the append-only file (AOF) rewriting performance for large-sized Redis databases. These instances reduce the latency and jitters that are caused when Redis calls forks to rewrite the AOF.
  • Persistent memory-optimized instances deliver high compatibility. These instances are compatible with most data structures and commands of native Redis databases.
ESSD-based instancesESSD-based instances are developed based on ESSDs and are compatible with core data structures and APIs of open source Redis. These instances can provide large-capacity, low-cost, and persistent database services. ESSD-based instances reduce costs and improve data reliability. In addition, ESSD-based instances reduce the amount of memory that is reserved for the forks of native Redis databases. This series type is suitable for scenarios that store warm and cold data, and require compatibility with open source Redis, large capacity, and high access performance.
Hybrid-storage instances (phased out)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 and provide a larger storage than ApsaraDB for Redis Community Edition instances. This allows hybrid-storage instances to balance performance with costs.
Note Hybrid-storage instances are phrased out. For more information, see End-of-Sale for ApsaraDB for Redis hybrid-storage instances. We recommend that you choose Persistent memory-optimized instances.

If you have purchased a hybrid-storage instance, you can submit a ticket to migrate the data of the instance.

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.

DRAM-based instances of the ApsaraDB for Redis Enhanced Edition (Tair)

Table 1. DRAM-based instances that run Redis 6.0
Minor versionUpdate levelRelease dateTypeDescription
6.2.3.2HIGH2023-01-13Fixed issue
  • The issue concerning slow deletion of expired data from cluster instances after the number of data shards is changed is fixed.
6.2.3.1LOW2023-01-04Feature optimization
  • The stability of high availability is enhanced for read/write splitting instances.
6.2.3.0LOW2022-12-26Feature optimization
  • TairVector is available for cluster instances in proxy mode. Additionally, the FLOAT16 data type and queries with multiple vector indexes are supported.
6.2.2.0LOW2022-11-22Feature optimization
  • The Jaccard distance formula is supported for TairVector.
  • The index_data_size and attribute_data_size parameters can be used in TairVector to calculate the memory usage of each index.
6.2.1.5LOW2022-11-14Feature optimization
  • The blocking issue of APIs is fixed to enhance the service stability.
6.2.1.3LOW2022-10-28Feature optimization
  • The stability of TairVector is enhanced.
6.2.1.2LOW2022-10-14Feature optimization
  • The stability of TairVector is enhanced.
6.2.1.1LOW2022-10-13First release
  • Redis 6.2.1.1 is supported. DRAM-based instances are compatible with Redis 6.2 and self-developed Tair data modules (except for TairSearch).
  • Slow queries that involve the KEYS, SMEMBERS, HGETALL, or EXHGETALL command can be identified and isolated.
  • Performance is optimized. Compared with commands run on ApsaraDB for Redis Community Edition instances, such as Pub/Sub commands and Lua commands, those run on Tair DRAM-based instances that use Redis 6.2.1.1 and have the same specifications enjoy two times the performance.
  • TairVector is released. TairVector is a self-developed vector search data module that supports the Hierarchical Navigable Small World (HNSW) and Flat Search indexing algorithms. It provides high-performance real-time vector database service that combines storage and search capabilities.
Table 2. DRAM-based instances that run Redis 5.0
Minor versionUpdate levelRelease dateTypeDescription
5.0.25LOW2023-01-13Feature optimization
  • The lowercase parameter is available for term and terms queries in TairSearch.
5.0.22MEDIUM2022-11-02Feature optimization
  • The IK and Pattern tokenizers are supported for TairSearch.
  • The stability is enhanced.
5.0.21LOW2022-11-02Feature optimization
  • The stability is enhanced.
5.0.18LOW2022-09-29Feature optimization
  • The stability of data parsing and persistence in TairSearch is enhanced.
  • The pipelining of the query builder client is supported for TairSearch.
5.0.15LOW2022-08-29Feature optimization
  • The MSEARCH feature of TairSearch is available.
  • The stability is enhanced for multi-thread writing of TairSearch.
  • The stability of instances in a cluster architecture is enhanced.
5.0.10LOW2022-07-28Feature optimization
  • The stability is enhanced.
5.0.9LOW2022-07-27Feature optimization
  • The stability is enhanced when child instances of a distributed instance are scaled.
  • The accuracy of sort is improved in TairSearch.
  • The query efficiency is improved for sparse documents in TairSearch.
1.9.7LOW2022-12-26Feature optimization
  • The stability of TairSearch is enhanced.
1.9.6LOW2022-11-02Feature optimization
  • The stability of TairTS is enhanced.
1.9.4LOW2022-08-24Feature optimization
  • The process of starting a cluster instance is optimized.
1.8.9LOW2022-06-07Feature optimization
  • The service stability is improved for instances that have the direct connection mode enabled.
1.8.8LOW2022-06-01Feature optimization
  • TairSearch is updated to improve the efficiency of JOIN queries.
1.8.5HIGH2022-05-24Security hardening
  • The configuration change stability is improved for cluster instances that have the direct connection mode enabled.
  • The aggregation feature is supported in TairSearch to improve document write efficiency.
1.8.4LOW2022-05-17Feature optimization
  • The stability and execution efficiency of TairSearch are improved.
1.8.3LOW2022-04-28Feature optimization
  • The stability of TairTS is enhanced.
1.8.2HIGH2022-04-22Security 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.
Feature optimization
  • The query efficiency of TairSearch is optimized.
1.8.1LOW2022-04-20Feature optimization
  • TairRoaring V2.2 is available.
1.7.28LOW2022-03-24Feature optimization
  • Statistics of Tair module commands can be collected and presented in latency histograms.
1.7.27LOW2022-03-11Feature optimization
  • TairRoaring V2 is available.
  • TairSearch is available.
1.7.20MEDIUM2022-01-04Feature optimization
  • The performance of TairRoaring is optimized.
1.7.17LOW2021-11-29Feature optimization
  • The following issue is fixed: Cluster instances may fail to be restarted in specific scenarios.
Note This feature optimization is supported only by performance-enhanced cluster instances that use cloud disks.
1.7.16LOW2021-11-24Feature optimization
  • The following issue is fixed: Statistics of SPOP commands are not collected when the real-time key analysis feature is used.
1.7.12MEDIUM2021-10-26Feature optimization
  • The following issue is fixed to enhance stability: An excessive number of slow logs are recorded during configuration changes of cluster instances.
1.7.11MEDIUM2021-10-15Feature optimization
  • Transparent Data Encryption (TDE) information can be included in the output of the INFO command.
  • The stability is enhanced.
1.7.9LOW2021-10-13Feature optimization
  • The autonomous capabilities of implementing imperceptible slot migration during configuration changes of cluster instances are enhanced.
1.7.8MEDIUM2021-09-26Feature optimization
  • The ray casting algorithm is optimized for TairGIS to yield more precise search results when you run the GIS.CONTAINS command.
1.7.7MEDIUM2021-09-13Feature optimization
  • TairRoaring is available.
  • The stability is enhanced.
1.7.6MEDIUM2021-08-30Feature optimization
  • Memory leaks that may occur during the persistence of append-only file (AOF) rewrites are fixed.
  • Statistics of queries per second (QPS) are classified. Three types of QPS can be calculated: read QPS, write QPS, and other QPS.
1.7.5MEDIUM2021-08-16Feature optimization
  • The reliability of imperceptible slot migration is enhanced to strengthen stability.
1.7.4HIGH2021-08-11Fixed issue
  • The following issue is fixed: Configuration changes may fail when the direct connection mode is enabled for cluster instances.
1.7.2MEDIUM2021-07-27Feature optimization
  • The stability is enhanced.
1.7.1MEDIUM2021-07-20New feature
  • TDE can be used to perform real-time I/O encryption and decryption on Redis Database (RDB) files.
Feature optimization
  • The memory usage of TairHash is optimized.
1.6.15MEDIUM2021-07-12Feature optimization
  • The stability is enhanced.
1.6.9 LOW2021-06-22New feature
  • Latency histograms are supported.
1.6.6MEDIUM2021-06-08 Feature optimization
  • The stability is enhanced.
1.6.3LOW2021-05-17New feature
  • Specific functions of keys can be retained based on keys or key patterns when data is cleared. This feature can be used in the following scenarios:
    • Restore specific keys or key patterns when point-in-time data restoration is performed by using the data flashback feature.
    • Delete or retain the keyspace content based on keys or key patterns.
1.6.2MEDIUM2021-04-25Feature 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 that use direct connection mode.
  • The format of large keys is optimized.
1.6.1MEDIUM2021-04-08New feature
  • By default, the statistics feature is enabled for large keys.
  • The GT parameter is supported for TairString.
Feature optimization
  • The capabilities to migrate slots and implement imperceptible scaling are improved.
1.5.1HIGH2021-03-15Fixed issue
  • The issue that the real-time statistics of large keys become inaccurate when keys with the same name are written is fixed.
1.5.0MEDIUM2021-02-22New feature
  • Statistics of large keys can be collected in real time.
Feature optimization
  • The failure 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.16HIGH2021-01-11New feature
  • Metadata can be cleared after an active geo-redundancy link becomes available. The link is built based on Global Distributed Cache for Redis or Data Transmission Service (DTS). This accelerates subsequent synchronization operations.
Fixed issue
  • Memory leaks that may occur when the FLUSHALL command is frequently run when TairHash is used are fixed.
1.4.13LOW2020-11-27New feature
  • When the illegal address error message is returned, the IP address of the client can be included in the error message.Tair An IP address whitelist can be configured for your instance based on the IP address prompt.Tair
    Figure 2. IP address prompt
    IP address prompt
1.4.12MEDIUM2020-11-26New feature
  • Flags such as FLAGS can be used in the syntax of TairString. This syntax is compatible with Memcached semantics.
Feature optimization
  • The failure detection capability of HA systems is improved.
    Note We recommend that you update the minor version to 1.5.0 or later for the latest optimization for this feature.
1.4.9HIGH2020-10-22Fixed issue
  • Correct binary logs can be generated when TairString data expires. This prevents data inconsistency between the master and replica nodes.
  • The abnormal switchover of HA systems is fixed. This issue occurs when TairHash still uses the active expire algorithm in read-only scenarios.
  • The following issue is fixed: The system may not respond when an instance that was forcefully stopped is restarted.
  • The following issue is fixed: Expired keys are deleted when RDB files are loaded to instances that have the data flashback feature enabled.
1.4.8HIGH2020-10-14Fixed issue
  • Memory leaks that may occur when specific modules are loading are fixed.
1.4.7MEDIUM2020-10-12Feature optimization
  • The output of the CLUSTER NODES command can be stored in the cache. This accelerates the command execution.
1.4.6MEDIUM2020-09-28Feature optimization
  • The processing capabilities of specific modules are improved in specific scenarios.
1.4.1MEDIUM2020-09-08New feature
  • The IP addresses of clients can be passed through to operational logs and audit logs by proxy nodes. This helps you interpret logs and identify clients that have issues.
Feature optimization
  • The data collection capability is improved to minimize the impact on data shards when a large number of connections are queued up and I/O threads are busy.
1.3.17MEDIUM2020-08-04Feature optimization
  • The latency is reduced when DTS is used to implement two-way data synchronization.
1.3.16HIGH2020-07-19New feature
  • The security group feature provided by Elastic Compute Service (ECS) is supported to simplify O&M. To allow ECS instances to access a Tair instance, you can add the security groups to which the ECS instances belong to the instance. You do not need to manually add the IP addresses of the ECS instances to the whitelists of the instance.
  • The TairString module is updated to support more API operations (flags) that are compatible with Memcached semantics.
Fixed issue
  • The following issue is fixed: The BGREWRITEAOF command is interrupted when you use the data flashback feature to restore data to a point in time.
  • Latency flag bits in audit logs can be modified to help you identify these bits in master and replica audit logs.
1.3.9MEDIUM2020-06-19Feature optimization
  • Saved point metadata can be automatically cleared when data is cleared. This way, replicators can be quickly restored in scenarios where multi-way data synchronization is implemented based on Global Distributed Cache for Redis or DTS.
1.3.7LOW2020-05-19New feature
  • The Replication part in the output of the INFO command shows role information, such as role:master. This allows Redisson clients to call the role information in specific scenarios.
1.3.6MEDIUM2020-05-19New feature
  • Statistics of hotkeys can be regularly recorded in logs.
  • The data statistics feature is available for performance metrics. This feature allows the system to differentiate the QPS that are generated in read, write, and read/write synchronization operations. This improves the accuracy of the statistics.
Feature optimization
  • The kernel capacity to restore data to a point in time by using data flashback is optimized to simplify data restoration.
  • Commands such as AUTH, ADMINAUTH, and CONFIG do not record sensitive information when these commands are used. This improves data security.
1.3.5HIGH2020-04-22Fixed issue
  • The issue that deadlocks may occur when multi-threaded engines asynchronously close client connections is fixed.
  • The issue that file descriptors in engines cannot linearly expand is fixed.
1.3.3HIGH2020-04-22New feature
  • The 64-bit hash algorithm can be applied to TairBloom.
  • The final memory usage of TairBloom can be estimated to allow the system to record more accurate memory statistics.
  • The exhgetAll2 interface can be used in TairHash to revise command output formats.
Fixed issue
  • The error message that is returned by instances when an whitelist is improperly configured is changed from (error) ERR invalid password to (error) ERR illegal address.
  • Memory leaks that may occur when you use TairGIS to manage multiple polygons are fixed.
  • The issue that the default path for TairDoc is incorrect is fixed.
  • The issue that Pub and Sub commands may compete for resources on multi-threaded engines is fixed.
1.3.1HIGH2020-04-03New 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 accidental operations, simplify O&M, and protect databases in real time.Tair
  • TairGIS can be compatible with Redis GEO commands.
  • TairBloom can be used in capacity security validation for the BFRESERVE interface.
  • TairHash supports the following new features:
    • The NOACTIVE parameter is added to multiple commands including EXHSET, EXHEXPIRE, EXHINCRBY, and EXHINCRBYFLOAT. This parameter can reduce memory overheads in specific scenarios.
    • The MAX and MIN parameters are added to the EXHINCRBY command to define the upper and lower boundaries of the value range.
    • The noexp parameter is added to the EXHLEN command to return the true length of the EXHLEN command.
  • The HINCRBY and HINCRBYFLOAT commands are supported for the hash structure. The transaction processing capability of these commands can be used to increase or decrease different fields that constitute a key at the same time.
Feature optimization
  • The use of data modules is optimized.
  • The performance is enhanced when the JedisCluster client runs the MGET or MSET command on cluster instances.
Fixed issue
  • The following issue is fixed: Binary logs take up more space than can be provided by an instance.
  • The issue that the system may not respond when hotkeys are evicted is fixed.
  • The issue that the system may not respond due to double deallocation in TairHash is fixed.
  • The issue that the system may not respond due to use-after-free (UAF) is fixed. This issue occurs when the audit log feature is disabled.
1.0.10LOW2020-02-19New feature
  • The BITFIELD_RO command is added. This command significantly optimizes the performance of the BITFIELD command in read/write splitting scenarios.
    Note If the BITFIELD command contains only the get parameter, proxy nodes convert the command into the BITFIELD_RO command and route the new command to multiple backend data shards.
1.0.9HIGH2020-02-19Fixed issue
  • The following issue is fixed: The replication process stops when specific complex commands in Lua scripts are run.
1.0.8HIGH2020-02-10Feature optimization
  • The algorithm and performance related to traffic throttling are improved.
Fixed issue
  • The issue that the service stops because the congestion of client output buffers triggers server overload protection is fixed.
1.0.5HIGH2020-02-01New feature
  • Global Distributed Cache is supported. Global Distributed Cache is an active geo-redundancy database system developed in-house. Global Distributed Cache supports business scenarios in which multiple sites in different regions provide services at the same time. This system also helps enterprises replicate the active geo-redundancy architecture of Alibaba.
  • Binary logs and their protocols are available to support capabilities such as active geo-redundancy.
Fixed issue
  • The issue that the output of the INFO command can contain the cluster_enabled information when the direct connection mode is used is fixed. This allows specific SDKs to automatically negotiate to enter the cluster mode.
  • The issue that the number of clients that are being managed is calculated inaccurately is fixed.
  • The issue that the system may not respond when a client is released is fixed.
  • The issue that the system may not respond when a pipeline contains complex commands is fixed.
0.2.9HIGH2020-01-06Feature optimization
  • The memory usage of TairHash is optimized.
Fixed issue
  • The issue that the system may not respond when traffic throttling is executed is fixed.
0.2.7HIGH2019-12-23New feature
  • The direct connection mode is supported. Clients can bypass proxy nodes to connect to instances by using private endpoints. This is similar to the connection to open source Redis clusters. The direct connection mode can reduce communication overheads and further improve the response speed.
  • The identification logic for hotkeys is supported. This allows hotkeys to be accurately identified. The memory usage of hotkeys is also optimized.
  • The EXCAS command is supported in optimistic locking scenarios.
Fixed issue
  • The core dump issue that may occur when pipelines are used is fixed.
0.2.3LOW2019-12-03First release

DRAM-based instances of ApsaraDB for Redis Enhanced Edition (Tair) are suitable for business scenarios that require high concurrency, high performance, and a large number of read and write operations on hot data. Compared with ApsaraDB for Redis Community Edition instances, DRAM-based instances have the following advantages:

  • Performance-enhanced instances use the multi-threading model and provide read and write performance approximately three times those of ApsaraDB for Redis Community Edition instances with the same specifications.
  • Performance-enhanced instances provide multiple enhanced data modules, such as TairString (including CAS and CAD commands), TairHash, TairGIS, TairBloom, and TairDoc. These modules help you simplify code, improve business performance, and allow you to focus on innovation.

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

Minor versionUpdate levelRelease dateTypeDescription
1.2.5.1LOW2022-09-21Fixed issue
  • Vulnerabilities of TairCpc V1.2.5 are fixed. These vulnerabilities may cause instance exceptions.
    Note We recommend that you update your instance that uses TairCpc V1.2.5 to this version.
  • The stability is enhanced.
1.2.5MEDIUM2022-08-31Feature optimization
  • The extension policies for primary hash tables are optimized.
  • The performance of FLUSHALL and FLUSHDB commands is optimized.
  • The performance of the rehashing function is optimized.
  • The stability is enhanced.
1.2.4.1LOW2022-07-28Fixed issue
  • The issue that the GETBIT command may cause instance exceptions is fixed. This issue happens in V1.2.4.
    Note We recommend that you update your instance to this minor version.
1.2.4LOW2022-07-18Feature optimization
  • The RENAME and MOVE commands are supported by using the pena_rename_move_compatible_enabled parameter. The time complexity of the two commands is O(n) in Tair, which differs from that of the two commands in open source Redis.
  • The stability is enhanced when cluster instances are scaled.
  • The performance of specific commands is improved to address slow execution issues on large keys. The commands include SETBIT, SETRANGE, APPEND, and BITFIELD.
1.2.3.4LOW2022-07-14Fixed issue
  • The Errorstats - Selected field returned by the INFO command can be deleted.
  • Latency histograms are optimized.
  • The stability of semi-synchronous data replication is enhanced.
  • The following issue is fixed: An error may be returned when commands such as ZUNIONSTORE or ZINTERSTORE are run on cluster instances that have the proxy mode enabled.
  • The following issue is fixed: The SORT command may cause inaccurate calculation of persistent memory usage in specific scenarios.
Feature optimization
  • The redis_version value is changed to 6.0.9 in the INFO command output.
1.2.3.3LOW2022-05-12New feature
  • TairCpc is available.
1.2.3.2HIGH2022-04-24Fixed issue
  • The following issue is fixed: The key eviction order is abnormal when the MAXMEMORY_VOLATILE_TTL policy is specified for key eviction.
  • The process of adding or deleting nodes for a cluster instance is optimized.
  • The stability of semi-synchronous data replication is enhanced.
1.2.3.1LOW2022-03-31Feature optimization
  • The following issue is fixed: CAS commands cannot be persisted.
  • The following issue is fixed: Client IP addresses cannot be displayed in slow and audit logs of cluster instances.
  • The stability is enhanced.
1.2.3MEDIUM2022-03-03New feature
  • TairString is available.
  • STREAM is supported.
  • The intset encoding is supported for SETs to reduce memory overheads.
  • Data eviction policies are supported.
  • The performance is optimized, and the stability is enhanced.
Fixed issue
  • The following issue is fixed: SPOP command statistics are not collected when the real-time key analysis feature is used.
1.2.2.4LOW2022-01-21Feature optimization
  • Storage space occupied by large values is optimized to reduce used persistent storage.
1.2.2.3HIGH2021-12-30Feature optimization
  • Tail latency that takes place during data writes is optimized.
  • The stability is enhanced.
1.2.2.2HIGH2021-12-14Fixed issue
  • The following issue is fixed: In specific scenarios, the usage of lists and hashes cannot be correctly calculated.
1.2.2.1LOW2021-10-21Feature optimization
  • The stability is enhanced.
1.2.2HIGH2021-10-20Feature update
  • The speed at which cluster instances are scaled can be adaptively controlled.
    Note During scaling operations, the speed at which old data is cleared is well adapted to instance loads. For example, more CPU cores are used for clearance in low-load scenarios to increase the clearance speed. This feature keeps the CPU utilization at a high level during scaling operations but does not affect service availability.
  • The performance of commands such as CLUSTER NODES is optimized for large cluster instances.
Fixed issue
  • The issue that abnormal slow logs are generated during scaling of cluster instances is fixed.
  • The stability is enhanced.
1.2.0LOW2021-09-21Feature update
  • The storage of the LIST, HASH, SET, and ZSET data structures is optimized to reduce their usage of memory and persistent memory.
1.1.8LOW2021-08-17Feature update
  • Persistent memory can be fully utilized when memory is exhausted in specific scenarios.
  • The stability is enhanced.
1.1.7LOW2021-08-02New feature
  • Semi-synchronous data replication is supported. By default, this feature is disabled. If you want to enable this feature, submit a ticket.
    Note If this feature is enabled, logs are transmitted from a master node to a replica node after the data update that the client initiates is complete on the master node. 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 the communication between a master node and a replica node is abnormal, semi-synchronous replication degrades to asynchronous replication.
  • In the output of the INFO command, the redis_version value is changed to 4.9.9 and the pena_version parameter is added to indicate the minor version.
1.1.6.1MEDIUM2021-06-10Feature update
  • The stability is enhanced.
1.1.6MEDIUM2021-05-08New feature
  • Imperceptible scaling operations are supported. This allows slots to be migrated without perceptible impacts on your business.
Feature optimization
  • Ziplist encoding is supported in HASH and ZSET data structures to reduce memory overheads.
  • The failure detection capability of HA systems is improved.
  • Data migration of large cluster instances is optimized. Large cluster instances refer to instances that have a large number of data shards.
  • The scaling stability of the cluster architecture is improved.
1.1.5MEDIUM2021-01-15New feature
  • Cluster instances are supported. These instances eliminate performance bottlenecks caused by the single-threading model of open source Redis. You can use cluster instances to support high-performance and large-capacity scenarios.
  • The minor version of an instance can be used as the redis_version value in the output of the INFO command.
Feature optimization
  • The stability is enhanced.
1.1.4MEDIUM2020-10-28New feature
  • The usage of persistent memory can be included in the command output when you run the INFO command by using a standard account.
Feature optimization
  • The space occupied by embstr encoding is decreased to reduce memory overheads.
  • The stability is enhanced.
1.1.3LOW2020-09-16First release

Persistent memory-optimized instances of the ApsaraDB for Redis Enhanced Edition (Tair) are an in-memory database service developed based on persistent memory. These instances are compatible with open source Redis and provide large capacity. These instances have the following benefits:

  • A persistent memory-optimized instance costs about 30% less than an ApsaraDB for Redis Community Edition instance.
  • In scenarios where advanced memory specifications are used, specific issues can be resolved. These issues include high latency, high network jitter, and slow service data loading during fork operations that are triggered by AOF rewrites. You are not confronted with the trade-off between performance and persistence.
  • Persistent memory-optimized instances support command-level persistence. A response is returned for each persisted write operation.
  • Persistent memory-optimized instances are compatible with most of the data structures and interfaces of open source Redis. The persistence of data structures except for STREAM is supported.

Tair ESSD-based instances

Minor versionUpdate levelRelease dateTypeDescription
2.3.2HIGH2022-12-22Fixed issue
  • The following issue is fixed: The system may crash when the BRPOP, BLPOP, and BRPOPLPUSH commands are run.
2.3.1MEDIUM2022-09-14New feature
  • The transaction feature is supported. The MULTI and EXEC commands can be used in transactions. You can use the txn-isolation-lock parameter to manage this feature.
  • The Lua scripting feature is supported. The EVAL, EVALSHA, and SCRIPT commands can be used to manage Lua scripts. You can use the txn-isolation-lock and #no_loose_lua-strict-mode parameters to manage this feature.
  • Commands that manage bitmaps are supported. These commands include BITCOUNT, BITFIELD, BITOP, BITPOS, GETBIT, and SETBIT.
Feature optimization
  • The stability of data synchronization between master and replica nodes is optimized.
2.2.22MEDIUM2022-08-10Feature optimization
  • The continuous read and write performance of instances that contain terabytes of data is optimized.
2.2.15HIGH2022-06-06Fixed issue
  • The stability is enhanced.
2.1.13LOW2022-05-05Feature optimization
  • The stability of data synchronization between master and replica nodes is optimized.
2.1.12LOW2022-04-26Feature optimization
  • The stability of data synchronization between master and replica nodes is optimized.
2.1.10LOW2022-04-14Feature optimization
  • The efficiency of synchronization between master and replica nodes is optimized to provide higher throughput with lower latency.
  • The resource usage of compact operations that are generated when a large number of large keys concurrently expire is optimized.
2.1.7LOW2021-08-12Feature optimization
  • The speed of master-replica switchover is optimized to improve stability. Master-replica switchover is also known as proactive HA.
2.1.5HIGH2021-07-13Fixed issue
  • The issue that binary logs occupy a large amount of space is fixed.
2.1.4MEDIUM2021-07-07Feature optimization
  • The storage parameters of ESSD-based instances that have terabytes of capacity are optimized to improve performance.
  • The stability is enhanced.
2.1.0LOW2021-05-26New feature
  • The canary release of the transaction feature is supported. The MULTI and EXEC commands can be used in transactions.
  • The canary release of the Lua scripting feature is supported. The EVAL, EVALSHA, and SCRIPT commands can be used to manage Lua scripts.
2.0.13LOW2021-04-24New feature
  • Notifications about keyspace events can be sent.
1.2.17HIGH2021-02-04Fixed issue
  • The following issue is fixed: In specific cases, the FLUSHALL command may cause data inconsistency between master and replica nodes.
1.2.16HIGH2021-01-29Fixed issue
  • The following issue is fixed to ensure data consistency between master and replica nodes: In specific cases, a master node and a replica node cannot be automatically reconnected after a disconnection.
1.2.15MEDIUM2021-01-20New 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.14LOW2020-12-31New feature
  • Data verification for master and replica nodes is added.
1.2.13HIGH2020-12-31Fixed issue
  • The defects of the RESTORE command that emerge in specific scenarios are fixed.
1.2.12MEDIUM2020-12-23Feature optimization
  • The FLUSHALL and FLUSHDB commands cannot be run in serial.
1.2.11MEDIUM2020-12-10Feature optimization
  • Memory management is optimized.
1.2.10LOW2020-12-04New feature
  • Password-free access over a virtual private cloud (VPC) is supported.
  • To prevent out of memory (OOM) errors caused by large transactions, the size of a single transaction can be limited by using the max-write-batch-size parameter.
1.2.9MEDIUM2020-11-27Feature optimization
  • The redis_version parameter is added to the output of the INFO command.
1.2.8HIGH2020-11-20Fixed issue
  • The issue that the number of connections is incorrectly calculated is fixed.
  • The issue that the number of keys is incorrectly calculated when the RESTORE command is run is fixed.
1.2.7HIGH2020-10-28Fixed issue
  • The issue that unexpected quits occur when the SETRANGE command is run is fixed.
  • The issue that exceptions occur when keys are empty strings is fixed.
1.2.6HIGH2020-09-28Fixed issue
  • The following issue is fixed: Connection management logs rapidly increase.
1.2.5HIGH2020-09-27Fixed issue
  • The following issue is fixed: Operational logs rapidly increase.
1.2.4HIGH2020-09-27Feature optimization
  • The stability of data synchronization between master and replica nodes is improved.
  • The scanning performance for members of complex data structures is optimized.
Fixed issue
  • The following issue is fixed: The ZADD and ZINCR commands are inconsistent with those of open source Redis, and semantic errors may occur when multiple duplicate members are managed.
  • The following issue is fixed: nil is returned for empty strings when the MGET command is run.
1.2.3LOW2020-09-27First release

ESSD-based 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. These instances provide high-capacity, low-cost, and persistent database services. ESSD-based instances have the following benefits:

  • ESSD-based instances store data in cloud disks to implement data persistence at a cost that can be as low as 15% that of ApsaraDB for Redis Community Edition instances.
  • ESSD-based instances use multiple I/O threads and worker nodes to improve throughput on each server and support replication of binary logs between master and replica nodes.
  • ESSD-based instances are compatible with most of the open source Redis commands.
  • ESSD-based instances reduce the amount of memory that is reserved for the forks of open source Redis.