Alibaba Cloud releases minor versions for ApsaraDB for Redis proxy nodes 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 proxy nodes. We recommend that you update the minor version of proxy nodes during off-peak hours.

View or update the minor version of proxy nodes

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 of proxy nodes
View the minor version of proxy nodes
Note
  • The system checks the minor version of proxy nodes that belong to your instance. If these proxy nodes are of the latest minor version, the Upgrade Proxy 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.

Overview of proxy nodes

Cluster instances and read/write splitting instances of ApsaraDB for Redis use proxy nodes to route commands, balance loads, and perform failovers. For more information, see Cluster master-replica instances and Read/write splitting instances. If you understand how proxy nodes route commands and handle specific commands, you can understand how to design more effective business systems. For more information about proxy nodes, see Features of proxy nodes.

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.

6.8.x

Minor version Update level Release date Type Description
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. For more information, see TairSearch.
  • New commands of TairRoaring V2.2 are supported. For more information, see TairRoaring.
6.8.0 MEDIUM 2022-04-01 New feature
  • Specific TairZset commands are supported. For more information, see TairZset.
  • Specific TairRoaring commands are supported. For more information, see TairRoaring.
  • 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. For more information about the parameter, see Supported parameters.
  • The following issue is fixed: The CROSSSLOT error occurs when the SMOVE command is run.

6.7.x

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.
  • The following issue is fixed: An error message is returned when the SDIFF or SDIFFSTORE command is run on instances that use specific minor versions under Redis 5.0.
6.7.7 LOW 2022-01-30 Feature optimization
  • The stability is enhanced.
6.7.6 LOW 2022-01-20 Feature optimization
  • The 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, a node is not repeatedly retrieved when the RANDOMKEY command is run for several times.
Fixed issue
  • The following issue is fixed: The aggregations that derive from info commandstats on performance-enhanced instances encounter errors.
6.7.4 MEDIUM 2021-12-20 Feature optimization
  • The 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
  • The stability is enhanced.
6.7.1 MEDIUM 2021-11-23 Feature optimization
  • The stability is enhanced.

6.6.x

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 fail 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
  • The stability is enhanced.
6.6.11 MEDIUM 2021-10-11 Feature optimization
  • The 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
  • The 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
  • The 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.

6.5.x

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 special 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 of the channels to which clients subscribe are migrated, proxy nodes close the client connections and reconnect to the clients. This ensures data consistency.
Feature optimization Proxy command processing is optimized. The following section describes the optimization:
  • Requests are resent to the address specified by the MOVED command when this command is run.
  • Proxy nodes do not route the commands without specified keys to the data shards that have empty slots.
6.5.5 HIGH 2021-03-05 Fixed issue
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 sent the most recent response can be recorded when slow 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.

6.4.x

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 packets, acknowledgment packets, and moved packets 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 Supported parameters.
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 specified specifications cannot be established by using Data Management (DMS). For more information, see Overview and What is ApsaraDB for Memcache?
  • 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 Jedis client.
Fixed issue
  • The following issue is fixed: The system incorrectly records slow logs by using the BZPOPMIN and XREAD commands. For more information, see View 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
  • Idle connections are automatically closed after a timeout configuration is added.
  • Statistics of slow 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 View 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 complete by using a Configserver node.

6.3.x

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 logs to facilitate troubleshooting. For more information, see View 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 Supported parameters.
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.