Tair (Redis® OSS-Compatible):Release notes for minor versions of proxy nodes

Minor version

Update level

Release date

Type

Description

7.0.13

LOW

2024-08-13

Feature optimization

• The #no_loose_sentinel-password-free-access configuration item can be used to enable password-free execution of the SUBSCRIBE command to subscribe to the +switch-master channel. The subscription is limited only to this channel.

7.0.12

MEDIUM

2024-07-24

Feature optimization

• The return values of API operations related to TairVector global indexes are optimized.

• The #no_loose_sentinel-password-free-access configuration item can be used to enable password-free access to Sentinel-related commands.

Fixed issue

• The following issue is fixed: Entries cannot be deleted from TairVector global indexes in some scenarios.

• The following issue is fixed: The SCRIPT EXISTS command returns 0 when the Lua script exists.

7.0.11

LOW

2024-07-04

Fixed issue

• The following issue is fixed: Configuration changes may fail after the JSON.SET or GIS.ADD command is run.

7.0.10

MEDIUM

2024-06-18

New feature

• The TairVector global index feature is available.

Feature optimization

• The time required to recover from master-replica synchronization failures is shortened to reduce the impact of the failures.

Fixed issue

• The issue that the query results in the TFT.MSEARCH command output are not sorted correctly is fixed.

• The following issue is fixed: When the number of keys of a single Tair instance or Tair shard is greater than 2^24, the SCAN command may fail to correctly return all matching keys.

7.0.9

MEDIUM

2024-04-08

Feature optimization

• REdis Serialization Protocol 2 (RESP2) and RESP3 are supported. You can use the HELLO command to switch between the protocols. However, to use the command, you must set the hello_enabled parameter to 1 in the configuration settings of the instance.

• The INFO command can return the pubsub_clients and tracking_clients fields. This optimization requires the instance to be compatible with Redis 6.0 or later.

Fixed issue

• The following issue is fixed: When the amount of response data being sent over an SSL or Transport Layer Security (TLS) connection is large enough to fill up the socket buffer, the connection may be closed.

7.0.8

MEDIUM

2024-02-09

Fixed issue

• The following issue is fixed: Consecutive SELECT commands within a transaction or SELECT commands at the end of a transaction can cause exceptions.

• The following issue is fixed: Exceptions occur at a low probability when you use the query cache feature to cache query results for hotkeys.

• The following issue is fixed: Requests sent over TLS or SSL connections may time out.

7.0.7

LOW

2023-12-15

Feature optimization

• The time required to recover from failures is shortened. Services can be quickly restored in the event of a database failure.

• When a blocking event occurs within a database connection, the response time (RT) for subsequent requests made over the same connection is optimized, preventing these requests from being incorrectly logged as slow queries.

• The TFT.EXPLAINSCORE command of TairSearch is supported.

7.0.6

LOW

2023-09-01

Feature optimization

• The CPU consumption of logging threads is reduced.

7.0.5

MEDIUM

2023-08-29

Fixed issue

• The following issue is fixed: Specific write commands of TairVector may be forwarded to read replicas in a read/write splitting instance.

• The following issue is fixed: ECHO commands are counted as write traffic.

7.0.4

LOW

2023-08-09

New feature

• TairVector commands are available for DRAM-based instances of Tair V23.8.0.0 that are compatible with Redis 6.0.

7.0.3

MEDIUM

2023-07-10

Feature optimization

• The number of connections required to handle transaction requests is decreased. When you issue transaction requests to your Redis instance without using the SELECT or WATCH command, multiple requests share the same connection.

Fixed issue

• The following issue is fixed: When multiple SELECT commands are run in a transaction request, the subsequent non-transactional requests that use the same connection may select incorrect databases.

7.0.2

MEDIUM

2023-05-11

New feature

• The TR.BITOP and TR.BITOPCARD commands are supported for keys that reside across slots.

• The following information is added to the outputs of the INFO and IINFO commands for a persistent memory-optimized instance: maxpmem (the maximum persistent memory of the instance) and used_pmem (the persistent memory usage). Unit: bytes.

• More than seven nested layers are supported for a response over RESP.

Feature optimization

• The limits of the proxy mode on the syntax of Lua scripts are optimized.

7.0.1

MEDIUM

2023-04-11

New feature

• Timed-out read requests can be automatically forwarded to other replica nodes.

• TLS 1.3 is supported.

• The TFT.ANALYZER and TFT.EXPLAINCOST commands of TairSearch are supported.

• Command outputs are changed from the encapsulated results on proxy nodes to the execution results from databases.

• The computing logic of channels upon incremental subscription is optimized to reduce CPU utilization.

Fixed issue

• The issue concerning a superfluous space at the end of one-line audit logs is fixed.

• The issue concerning memory leaks that may occur when the client uses an incorrect protocol is fixed.

7.0.0

MEDIUM

2023-03-09

New feature

• Commands of Redis 6.2 and 7.0 are supported.

• The TFT.ANALYZER command of TairSearch is supported.

Minor version

Update level

Release date

Type

Description

6.8.22

MEDIUM

2024-09-02

Fixed issue

• Stability is enhanced.

6.8.21

MEDIUM

2024-07-23

Fixed issue

• The following issue is fixed: Configuration changes may fail after the JSON.SET or GIS.ADD command is run.

• The following issue is fixed: The SCRIPT EXISTS command returns 0 when the Lua script exists.

6.8.20

MEDIUM

2024-06-24

New feature

• The compatibility between components is optimized.

6.8.19

MEDIUM

2024-06-04

Feature optimization

• The time required to recover from master-replica synchronization failures is shortened to reduce the impact of the failures.

Fixed issue

• The issue that the query results in the TFT.MSEARCH command output are not sorted correctly is fixed.

• The following issue is fixed: When the number of keys of a single Tair instance or Tair shard is greater than 2^24, the SCAN command may fail to correctly return all matching keys.

6.8.18

MEDIUM

2024-04-22

Fixed issue

• When a connection is being closed, the client can receive pending responses before the connection is completely closed.

6.8.17

MEDIUM

2024-03-28

Fixed issue

• The following issue is fixed: When the amount of response data being sent over an SSL or TLS connection is large enough to fill up the socket buffer, the connection may be closed.

6.8.16

MEDIUM

2024-01-26

Fixed issue

• The following issue is fixed: Requests sent over SSL or TLS connections may time out.

6.8.15

MEDIUM

2024-01-12

Fixed issue

• The following issue is fixed: Consecutive SELECT commands within a transaction or SELECT commands at the end of a transaction can cause exceptions.

• The following issue is fixed: The query cache feature may function abnormally.

6.8.14

MEDIUM

2023-11-16

Feature optimization

• The number of connections required to handle transaction requests is reduced. When you issue transaction requests to your instance without using the SELECT or WATCH command, multiple requests share the same connection.

• When a blocking event occurs within a database connection, the RT for subsequent requests made over the same connection is optimized, preventing these requests from being incorrectly logged as slow queries.

• The TFT.EXPLAINSCORE command of TairSearch is supported.

6.8.13

MEDIUM

2023-07-24

Fixed issue

• The following issue is fixed: When multiple SELECT commands are run in a transaction request, the subsequent non-transactional requests that use the same connection may select incorrect databases.

6.8.12

MEDIUM

2023-05-17

New feature

• The TR.BITOP and TR.BITOPCARD commands are supported for keys that reside across slots.

Feature optimization

• The limits of the proxy mode on the syntax of Lua scripts are optimized.

Fixed issue

• The issue concerning memory leaks that may occur when the client uses an incorrect protocol is fixed.

6.8.11

MEDIUM

2023-04-04

New feature

• TLS 1.3 is supported.

• The TFT.ANALYZER and TFT.EXPLAINCOST commands of TairSearch are supported.

Fixed issue

• The issue concerning a superfluous space at the end of one-line audit logs is fixed.

6.8.10

MEDIUM

2023-01-06

New feature

• TairVector is supported.

Fixed issue

• The issue that may cause filter aggregation errors in TairSearch is fixed.

• The following issue is fixed: After the ptod_enabled parameter is set to 1, the IP address of the client in audit logs becomes incorrect.

6.8.9

MEDIUM

2022-12-14

New feature

• The OS field is added to the output of the INFO command.

• The CLIENT KILL user command is supported.

Fixed issue

• The issue that may cause the MOVED command to return incomplete data is fixed. This prevents the failure to parse the client protocol.

6.8.8

MEDIUM

2022-11-15

New feature

• The BF.INFO command is supported.

• The EXHSCANUNORDER command of TairHash is supported.

• The maximum size of an audit log is changed from 4 KB to 2 KB.

Fixed issue

• The issue concerning incorrect IP addresses in audit logs of cloud-native instances in proxy mode is fixed.

6.8.7

LOW

2022-08-22

Feature optimization

• Stability is enhanced.

6.8.6

MEDIUM

2022-08-16

New feature

• Specific TairSearch commands are supported.

• The authentication in the AUTH user:password format is supported.

Feature optimization

• The issue concerning nested empty arrays caused by RESP3 is fixed.

6.8.4

MEDIUM

2022-07-20

New feature

• RESP3 can be resolved and forwarded, and the communication mode between proxy nodes and Tair instances can be changed by using the resp_version parameter.

6.8.2

MEDIUM

2022-06-14

Feature optimization

• The stability is improved, and specific crashes are fixed.

6.8.1

LOW

2022-04-19

New feature

• Specific TairSearch commands are supported.

• New commands of TairRoaring V2.2 are supported.

6.8.0

MEDIUM

2022-04-01

New feature

• Specific TairZset commands are supported.

• Specific TairRoaring commands are supported.

• The RC4 encryption algorithm is disabled for SSL certificates.

Fixed issue

• The following issue is fixed: After the ptod_enabled parameter is enabled, an exception occurs when the SDIFFSTORE, SINTERSTORE, SUNIONSTORE, ZINTERSTORE, or ZUNIONSTORE command is run.

• The following issue is fixed: The CROSSSLOT error occurs when the SMOVE command is run.

Minor version

Update level

Release date

Type

Description

6.7.9

MEDIUM

2022-03-05

Fixed issue

• The following issue is fixed: \n in the command output is truncated when the DBSIZE or KEYS command is run on instances that have abnormal nodes.

6.7.8

MEDIUM

2022-03-03

Fixed issue

• The following issue is fixed: The SCRIPT DEBUG command cannot be used.

• The following issue is fixed: The output score of the ZINTERSTORE or ZUNIONSTORE command has only six decimal places.

6.7.7

LOW

2022-01-30

Feature optimization

• Stability is enhanced.

6.7.6

LOW

2022-01-20

Feature optimization

• Stability is enhanced.

6.7.5

MEDIUM

2022-01-10

Feature optimization

• The RANDOMKEY command is optimized to retrieve a different random node each time. This way, if the RANDOMKEY command is run multiple times, it does not retrieve the same node repeatedly.

Fixed issue

• The following issue is fixed: The aggregations that derive from info commandstats on DRAM-based instances encounter errors.

6.7.4

MEDIUM

2021-12-20

Feature optimization

• Stability is enhanced.

6.7.3

MEDIUM

2021-12-15

Fixed issue

• The following issue is fixed: After an SSL connection is established for an instance, the first sent request may not receive a response.

6.7.2

LOW

2021-11-30

Feature optimization

• Stability is enhanced.

6.7.1

MEDIUM

2021-11-23

Feature optimization

• Stability is enhanced.

Minor version

Update level

Release date

Type

Description

6.6.14

MEDIUM

2021-11-01

Feature optimization

• The following issue is fixed: In the Elastic Compute Service (ECS) architecture, the ZINTERSTORE and ZUNIONSTORE commands may be unable to return responses when the split_multi_key_cmd_as_slot parameter is enabled.

6.6.13

MEDIUM

2021-10-22

Feature optimization

• The following issue is fixed: After the proxy query cache feature is enabled, hot upgrades may fail.

6.6.12

MEDIUM

2021-10-12

Feature optimization

• Stability is enhanced.

6.6.11

MEDIUM

2021-10-11

Feature optimization

• Stability is enhanced.

6.6.10

MEDIUM

2021-09-27

Fixed issue

• The following issue is fixed: An error message is returned when an ApsaraDB for Memcache instance processes only read or write requests.

6.6.9

MEDIUM

2021-09-06

Fixed issue

• The CVE-2021-3711 and CVE-2021-3712 vulnerabilities are fixed.

6.6.8

MEDIUM

2021-08-30

Feature optimization

• Stability is enhanced.

6.6.7

MEDIUM

2021-08-27

Feature optimization

• Memory leaks that occur when the statistics feature is enabled are fixed.

6.6.6

LOW

2021-08-13

Feature optimization

• Stability is enhanced.

6.6.5

LOW

2021-08-03

New feature

• The Memcached gateway mode is supported. This allows you to use the Memcached protocol to forward requests.

6.6.4

HIGH

2021-07-08

New feature

• The CLIENT LIST or CLIENT KILL command can be used to query or manage client connections by process.

Fixed issue

• The issue that TairZset commands do not support uppercase letters is fixed. For more information, see TairZset.

6.6.3

MEDIUM

2021-06-18

Feature optimization

• Internal management in cross-zone disaster recovery scenarios is optimized.

6.6.2

LOW

2021-06-08

New feature

• More internal commands of ApsaraDB for Redis are available.

6.6.1

LOW

2021-05-26

New feature

• The TairZset data structure is added. It allows you to sort score data of the DOUBLE type with respect to different dimensions. This data structure improves the data processing efficiency and is easy to use on the client side because you do not need to encode, decode, or encapsulate data. For more information, see TairZset.

6.6.0

LOW

2021-04-28

New feature

• The proxy query cache feature is added. After you enable this feature, proxy nodes cache the request and response data of hotkeys. If a proxy node receives a duplicate request within the validity period of cached data, the proxy node directly returns a response to the client without the need to interact with backend data shards. This feature reduces access skew that occurs when a large number of read requests for hotkeys are sent. For more information, see Use proxy query cache to address issues caused by hotkeys.

Minor version

Update level

Release date

Type

Description

6.5.9

HIGH

2021-04-21

Fixed issue

• The following issue is fixed: Infinite loops occur when the commands used to manage multiple keys are run in specific scenarios.

6.5.8

HIGH

2021-04-16

Fixed issue

• The following issue that occurs in 6.5.5 is fixed: Requests are out of order when multiple databases are requested. This minor version is a special version released based on 6.5.5.

6.5.7

HIGH

2021-04-16

Fixed issue

• The following issue is fixed: Requests are out of order when multiple databases are requested.

6.5.6

MEDIUM

2021-04-09

New feature

• The maximum number of data shards supported by the SCAN command increases from 256 to 1,024.

• If the slots to which clients subscribe are migrated, proxy nodes close the client connections and reconnect to clients. This ensures data consistency.

Feature optimization

Proxy command processing is optimized from the following aspects:

• Requests are resent to the address specified by the MOVED command when this command is run.

• Proxy nodes do not route commands that do not contain specified keys to data shards that have empty slots.

6.5.5

HIGH

2021-03-05

Fixed issue

• The following issue is fixed: Memory leaks may occur when distributed hash table (DHT) updates are triggered by master/replica switchovers or configuration changes. For more information, see Manually switch workloads from a master node to a replica node and Change the configurations of an instance.

6.5.4

HIGH

2021-02-07

Fixed issue

• The following issue is fixed: Memory leaks may occur when clients require a long time to receive responses.

6.5.3

HIGH

2021-01-21

New feature

• Variables can be used in the indexes of the KEYS array in Lua scripts.

Fixed issue

• The following issue is fixed: Memory leaks occur when the MULTI or BLOCK command is run on a cluster instance that has more than 32 data shards. For more information, see Cluster master-replica instances.

6.5.2

HIGH

2021-01-19

Fixed issue

• The following issue is fixed: Virtual IP addresses (VIPs) cannot be obtained by using sockets in alb enat mode.

6.5.1

LOW

2021-01-14

New feature

• The IP address of the data shard that sends the most recent response can be recorded when slow query logs record the commands used to manage multiple keys.

6.5.0

HIGH

2020-12-24

Fixed issue

• The following issue is fixed: The system may not respond when the GIS.GETALL command is run. For more information about this command, see TairGIS.

Minor version

Update level

Release date

Type

Description

6.4.10

MEDIUM

2020-12-01

Feature optimization

• The error message returned due to an invalid password is optimized to facilitate your understanding.

6.4.9

HIGH

2020-11-06

Fixed issue

• The following issue is fixed: The system does not respond when SSL encryption is enabled in multi-threading mode. For more information, see Configure SSL encryption.

• The following issue is fixed: The response protocol is incorrect due to channels that contain 0 when the UNSUBSCRIBE command is run.

6.4.8

HIGH

2020-10-21

Feature optimization

• Operational logs encode and then record binary requests for large packages, acknowledge packages, and moved packages to prevent garbled characters for logs.

Fixed issue

• The issue that the max_session_processing parameter cannot be dynamically configured is fixed. This parameter specifies the maximum number of pending requests that are allowed per connection. For more information about the parameter, see Parameters that can be configured for ApsaraDB for Redis instances.

6.4.7

MEDIUM

2020-10-09

Feature optimization

• The internal monitoring of proxy nodes is optimized.

6.4.6

HIGH

2020-09-30

Fixed issue

• The following issue is fixed: The SLOWLOG command that is run on a standard or cluster instance times out because the node roles are not initialized.

• The following issue is fixed: Connections to ApsaraDB for Memcache instances of specific specifications cannot be established by using Data Management (DMS). For more information, see What is ApsaraDB for Memcache? and What is DMS?

• The following issue is fixed: The system does not respond because no keys are specified when clients subscribe to __keyspace@0__.

6.4.5

LOW

2020-09-27

New feature

• More internal commands of ApsaraDB for Redis are available.

6.4.3

HIGH

2020-09-25

Feature optimization

• The special implementation of pipelines on the Jedis client is adapted to optimize the process to disable connections that are beyond the configured connection limit. For more information about Jedis connections, see Use a client to connect to an ApsaraDB for Redis instance.

Fixed issue

• The following issue is fixed: The system incorrectly records slow query logs by using the BZPOPMIN and XREAD commands. For more information, see Query slow logs.

6.4.2

HIGH

2020-09-09

Fixed issue

• The issue that idle connections are automatically closed after 1 minute is fixed.

6.4.1

MEDIUM

2020-08-25

New feature

• The timeout parameter is added. Idle connections are automatically closed after the specified timeout value.

• Statistics of slow query logs on read replicas can be collected. This indicates that the SLOWLOG command is sent to the master node and all read replicas. For more information, see Query slow logs.

Feature optimization

• The memory usage of connections supported by the PubSub and MONITOR commands is optimized to prevent a rapid increase in memory usage due to memory fragments.

• The capabilities of proxy nodes to handle new connections are improved.

6.4.0

HIGH

2020-08-18

Fixed issue

• The following issue is fixed: The system does not respond when you call the stat() function before configurations are completed by using a ConfigServer node.

Minor version

Update level

Release date

Type

Description

6.3.9

MEDIUM

2020-08-14

New feature

• The IP addresses of clients are recorded in slow query logs to facilitate troubleshooting. For more information, see Query slow logs.

Feature optimization

• The capabilities of proxy nodes to handle short-lived connections are improved.

6.3.8

HIGH

2020-07-24

Fixed issue

• The following issue is fixed: Memory usage increases because the vector::clear() function does not take effect.

6.3.7

HIGH

2020-07-13

Fixed issue

• The following issue is fixed: The system may not respond when you establish a connection after SSL encryption is enabled.

6.3.5

HIGH

2020-07-10

New feature

• Binary data in audit logs is encoded to improve log readability.

• The no_loose_statistics-ip-enable, no_loose_statistics-keys, and no_loose_statistics-cmds parameters are added. You can set the parameters to collect statistics of specific IP addresses, keys, and commands. For more information, see Parameters that can be configured for ApsaraDB for Redis instances.

Fixed issue

• The following issue is fixed: After a connection is closed, the system may not respond when the CheckExceedLimitAndClose command is run.

• The issue that the SSL encryption feature cannot be enabled is fixed.

6.3.4

HIGH

2020-05-21

Fixed issue

• The following issue is fixed: The system may not respond to subsequent requests due to empty packets such as \r\n.