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 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 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 does not exist 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.

Introduction to 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 cost. 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.

Series type Description
Performance-enhanced instances
  • Performance-enhanced instances use the multi-threading model to provide approximately three times the performance of ApsaraDB for Redis Community Edition instances with the same specifications.
  • Performance-enhanced instances provide multiple enhanced data structure modules such as TairString (including CAS and CAD commands), TairHash, TairGIS, TairBloom, TairDoc, TairTS, TairCpc, TairZset, and TairRoaring. Performance-enhanced instances eliminate concerns about storage structure and timeliness and allow you to focus on business development.
  • Performance-enhanced instances provide high compatibility. Performance-enhanced instances are fully compatible with open source Redis. You can switch from open source Redis to ApsaraDB for Redis without the need to modify application code.
  • Performance-enhanced instances provide a variety of enterprise-grade features such as data flashback, proxy query cache, and Global Distributed Cache for Redis. For more information, see Use data flashback to restore data by point in time, Use proxy query cache to address issues caused by hotkeys, and Overview.
Persistent memory-optimized instances Persistent memory-optimized instances adopt Intel Optane DC persistent memory to provide you with in-memory databases that have a large capacity and are compatible with open source Redis. A persistent memory-optimized instance persists each operation and does not use disks to implement data persistence. Compared with an ApsaraDB for Redis Community Edition instance, it reduces costs by up to 30% and delivers almost the same throughput and latency. This helps improve the reliability of business data.
Storage-optimized instances Storage-optimized instances were 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. 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 open source Redis. This series type applies to 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 strike a balance between performance and cost.
Note Hybrid-storage instances are discontinued. For more information, see Sales of ApsaraDB for Redis hybrid-storage instances are discontinued. We recommend that you use performance-enhanced instances that provide higher performance and more features.

If you have purchased s 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.

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

Minor version Update level Release date Type Description
1.7.27 LOW 2022-03-11 Feature optimization
1.7.20 MEDIUM 2022-01-04 Feature optimization
  • The performance of TairRoaring is optimized.
1.7.17 LOW 2021-11-29 Feature optimization
  • The following issue is fixed: Cluster instances may be unable to restart in some scenarios.
Note Only performance-enhanced instances that use cloud disks are available.
1.7.16 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.
1.7.12 MEDIUM 2021-10-26 Feature optimization
1.7.11 MEDIUM 2021-10-15 Feature optimization
  • Transparent Data Encryption (TDE) information is included in the output of the INFO command.
  • Stability is enhanced.
1.7.9 LOW 2021-10-13 Feature optimization
  • The autonomous capabilities of implementing imperceptible slot migration during cluster configuration changes are enhanced.
1.7.8 MEDIUM 2021-09-26 Feature optimization
  • The ray casting algorithm is optimized for the TairGIS data structure to yield more precise search results when you run the GIS.CONTAINS command.
1.7.7 MEDIUM 2021-09-13 Feature optimization
1.7.6 MEDIUM 2021-08-30 Feature optimization
  • Memory leaks that may occur during the append-only file (AOF) persistence of rewrites are fixed.
  • Statistical data of queries per second (QPS) is classified. Three types of QPS can be calculated: read QPS, write QPS, and other QPS.
1.7.5 MEDIUM 2021-08-16 Feature optimization
  • The reliability of imperceptible slot migration is enhanced to strengthen stability.
1.7.4 HIGH 2021-08-11 Fixed issue
  • The following issue is fixed: Configuration changes may fail when the direct connection mode is enabled for cluster instances.
1.7.2 MEDIUM 2021-07-27 Feature optimization
  • Stability is enhanced.
1.7.1 MEDIUM 2021-07-20 New 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. For more information, see TairHash commands.
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 large key pattern is optimized.
1.6.1 MEDIUM 2021-04-08 New feature
  • By default, the statistics feature is enabled for large keys.
  • TairString commands are available in the gt version. For more information, see TairString commands.
Feature optimization
  • The capabilities to migrate slots and implement imperceptible scaling are improved.
1.5.1 HIGH 2021-03-15 Fixed 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.0 MEDIUM 2021-02-22 New feature
  • Statistics of large keys can be collected 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 that may occur when the FLUSHALL command is frequently run in TairHash scenarios are fixed. For more information, see TairHash commands.
1.4.13 LOW 2020-11-27 New feature
  • When the illegal address error message is returned, the IP address of the client is 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
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 improved.
    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
  • Correct binlogs are generated when TairString commands expire. This prevents data inconsistency between the master and replica nodes.
  • Abnormal switchover of HA systems is fixed. This issue occurs when TairHash commands still use the active expire algorithm in read-only scenarios.
  • The following issue is fixed: The system may not respond when an instance is restarted after it is forcibly stopped.
  • The following issue is fixed: Expired keys are deleted when RDB files are loaded to ApsaraDB for Redis instances that have the data flashback feature enabled. For more information about the data flashback feature, see Use data flashback to restore data by point in time.
1.4.8 HIGH 2020-10-14 Fixed issue
  • Memory leaks that may occur when some modules are loaded are fixed.
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 nodes can pass through the IP addresses of clients 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 to simplify Q&M. You can grant permissions to ApsaraDB for Redis instances when you add the instances to security groups to which ECS instances belong. You do not need to manually enter the IP addresses of the ECS instances. 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
  • 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. For more information about the data flashback feature, see Use data flashback to restore data by point in time.
  • Latency flag bits in audit logs are modified to help you identify these bits in master and replica audit logs.
1.3.9 MEDIUM 2020-06-19 Feature optimization
1.3.7 LOW 2020-05-19 New 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 some scenarios.
1.3.6 MEDIUM 2020-05-19 New feature
  • Statistics about hotkeys are 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 capabilities for restoring data to a point in time are improved to simplify 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
  • The issue that deadlocks may occur when multi-threaded engines asynchronously disable client connections is fixed.
  • The issue that file descriptors in engines cannot linearly expand is fixed.
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 to allow the system to record more accurate memory statistics.
  • The exhgetAll2 interface is used in TairHash commands to revise command output formats.
Fixed issue
  • The error message that is returned by ApsaraDB for Redis when a 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 commands to manage multiple polygons are fixed.
  • The issue that the default path for TairDoc commands is incorrect is fixed.
  • The issue that Pub and Sub commands may compete in multi-threaded engines is fixed.
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 accidental 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 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 define the upper and lower boundaries of 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. The transaction processing capability of these commands can be used to increase and decrease different fields that constitute 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 on cluster instances with much higher performance.
Fixed issue
  • Binlog overflows are fixed.
  • 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 commands is fixed.
  • The issue that the system may not respond due to use-after-free (UAF) is fixed. The issue occurs when the audit log feature is disabled.
1.0.10 LOW 2020-02-19 New feature
  • The BITFIELD_RO command is added. This command significantly optimizes the performance of the BITFIELD command in read/write splitting scenarios.
    Note If BITFIELD commands contain only the get option, proxy nodes convert the commands to BITFIELD_RO commands and route these new commands to multiple backend data shards.
1.0.9 HIGH 2020-02-19 Fixed issue
  • The following issue is fixed: The replication process stops when some sophisticated 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
  • The issue that the service stops because the congestion of client output buffers triggers server overload protection is fixed.
1.0.5 HIGH 2020-02-01 New feature
  • Global Distributed Cache for Redis is supported. Global Distributed Cache for Redis 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. It helps enterprises replicate the active geo-redundancy architecture of Alibaba. For more information, see Overview.
  • Binlogs 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 some SDKs to automatically negotiate to enter the cluster mode. For more information, see Enable the direct connection mode.
  • The issue that the number of controlled clients is inaccurately calculated 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 sophisticated commands is fixed.
0.2.9 HIGH 2020-01-06 Feature optimization
Fixed issue
  • The issue that the system may not respond when traffic throttling is executed is fixed.
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 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 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 core dump issue that may occur when pipelines are used is fixed.
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 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, performance-enhanced instances have the following benefits:
  • Performance-enhanced instances use the multi-threading model and provide read and write performance approximately three times that of ApsaraDB for Redis Community Edition instances with the same specifications.
  • Performance-enhanced instances provide multiple enhanced data structure modules such as TairString (including CAS and CAD commands), TairHash, TairGIS, TairBloom, and TairDoc. These modules do not have strict requirements for the structure or validity period of storage and improve the efficiency of business development.

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

Minor version Update level Release date Type Description
1.2.3 MEDIUM 2022-03-03 New feature
  • TairString is supported. For more information, see TairString commands.
  • Streams are supported.
  • The intset encoding is supported for SETs to reduce memory overheads.
  • Data eviction policies are supported.
  • Performance is optimized, and stability is enhanced.
Fixed issue
  • The following issue is fixed: Statistics of SPOP commands are not collected when the real-time key analysis feature is used.
1.2.2.4 LOW 2022-01-21 Feature optimization
  • Storage space occupied by large values is optimized to reduce used persistent storage.
1.2.2.3 HIGH 2021-12-30 Feature optimization
  • Tail latency that takes place during data writes is optimized.
  • Stability is enhanced.
1.2.2.2 HIGH 2021-12-14 Fixed issue
  • The following issue is fixed: In special scenarios, the usage of lists and hashes is incorrectly calculated.
1.2.2.1 LOW 2021-10-21 Feature optimization
  • Stability is enhanced.
1.2.2 HIGH 2021-10-20 Feature 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.
  • Stability is enhanced.
1.2.0 LOW 2021-09-21 Feature 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.8 LOW 2021-08-17 Feature update
  • When memory is exhausted in some scenarios, persistent memory can be fully utilized.
  • Stability is enhanced.
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, 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 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
  • The hash and ZSET data structures support ziplist encoding to reduce memory overheads.
  • The liveness detection capability of HA systems is improved.
  • Data migration of large cluster instances is optimized. Large cluster instances indicate instances that have a large number of data shards.
  • The scaling stability of the cluster architecture is improved.
1.1.5 MEDIUM 2021-01-15 New feature
  • Cluster instances are supported. This eliminates performance bottlenecks caused by the single-threading model of open source Redis. You can use 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
  • The 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.
  • The 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. Persistent memory-optimized 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, issues such as high latency, high network jitter, and slow service data loading during fork operations triggered by 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 open source 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 Update level Release date Type Description
2.1.7 LOW 2021-08-12 Feature optimization
  • The speed of master-replica switchover is optimized to improve stability. Master-replica switchover is also known as proactive HA.
2.1.5 HIGH 2021-07-13 Fixed issue
  • The issue that binlogs occupy a large amount of space is fixed.
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
  • The following issue is fixed: In extreme cases, the FLUSHALL command may cause data inconsistency between master and replica nodes.
1.2.16 HIGH 2021-01-29 Fixed issue
  • The following issue is fixed to ensure data consistency between master and replica nodes: In extreme cases, a master node and a replica node cannot be automatically reconnected after a disconnection.
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 verification for master and replica nodes is added.
1.2.13 HIGH 2020-12-31 Fixed issue
  • The defects of the RESTORE command that emerge in specific scenarios are fixed.
1.2.12 MEDIUM 2020-12-23 Feature optimization
  • The FLUSHALL and FLUSHDB commands cannot be run in serial.
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 virtual private clouds (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 prevent 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 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.7 HIGH 2020-10-28 Fixed 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.6 HIGH 2020-09-28 Fixed issue
  • The issue of a sharp increase in connection management logs is fixed.
1.2.5 HIGH 2020-09-27 Fixed issue
  • The issue of a sharp increase in operational logs is fixed.
1.2.4 HIGH 2020-09-27 Feature optimization
  • The stability of data synchronization between master and replica nodes is improved.
  • The scanning performance for members that have sophisticated data structures is optimized.
Fixed issue
  • The following issue is fixed to prevent semantic errors that may occur when multiple duplicate members are managed: The ZADD and ZINCR commands are inconsistent with those of open source Redis.
  • The following issue is fixed: 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. These instances provide high-capacity, low-cost, and persistent database services. Storage-optimized instances have the following benefits:
  • Storage-optimized 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.
  • 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 open source Redis commands.
  • Storage-optimized instances reduce the amount of reserved memory that is required for the forks of open source Redis.