Alibaba Cloud releases minor versions for ApsaraDB for Redis proxy servers from time to time to provide more features, fix known issues, and improve user experience. This topic describes minor version updates of proxy servers. We recommend that you update minor versions of proxy servers during off-peak hours.

View or update the minor version of proxy servers

You can view the minor version of proxy servers that belong to the current 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 servers
View the minor version of proxy servers
Note
  • The system checks the minor version of proxy servers that belong to your instance. If these proxy servers are of the latest version, the Upgrade Proxy button does not exist or cannot be clicked.
  • Minor version updates may differ from region to region. The minor version of an instance displayed in the ApsaraDB for Redis console prevails.

Overview of proxy servers

Cluster instances and read/write splitting instances of ApsaraDB for Redis use proxy servers to route commands, balance loads, and perform failovers. For more information, see Cluster master-replica instances and Read/write splitting instances. This topic describes how proxy servers route commands and handle special commands. This helps you design more effective business systems. For more information, see Features of proxy servers.

Update levels

  • LOW: regular update. This level includes routine feature updates, such as adding a feature.
  • MEDIUM: recommended update. This level includes optimization of features and modules, such as optimizing a feature. Moreover, LOW-level updates are included in this level.
  • HIGH: important update. This level includes major updates that ensure stability or security, such as fixing a vulnerability or defect. Moreover, LOW-level and MEDIUM-level updates are included in this level.

6.6.x

Minor version number Update level Release date Type Description
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 and CLIENT KILL commands can show and manage process-level connections.
Fixed issue
  • Capital letters are not supported in TairZSET commands. For more information, see TairZSET commands.
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
  • Some internal commands are supported.
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 from different dimensions. This data structure improves the data processing efficiency and is also easy to use on the client side because you do not need to encode, decode, or encapsulate data. For more information, see TairZSET commands.
6.6.0 LOW 2021-04-28 New feature
  • The proxy query cache feature is added. After you enable this feature, proxy servers cache the request and response data of hotkeys. If a proxy server receives a duplicate request within the validity period of cached data, the proxy server directly returns a response to the client without the need to interact with backend data shards. This feature reduces skewed requests that occur when large amounts of read requests are sent by hotkeys. For more information, see Use proxy query cache to address issues caused by hotkeys.

6.5.x

Minor version number Update level Release date Type Description
6.5.9 HIGH 2021-04-21 Fixed issue
  • In special scenarios, commands that involve multiple keys fall into an infinite loop.
6.5.8 HIGH 2021-04-16 Fixed issue
  • Requests are out of order when multiple databases are selected. This version is a special version released on top of minor version 6.5.5.
6.5.7 HIGH 2021-04-16 Fixed issue
  • Requests are out of order when multiple databases are selected.
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.
  • When the slot that contains the subscribed channel is migrated, the proxy server closes the subscription connection to allow reconnection from the client. This ensures data consistency.
Feature optimization The mechanism to handle commands related to proxy servers is optimized. The following section describes detailed mechanism optimization:
  • Requests are resent to the address specified by the MOVED command when this command is run.
  • Data shards with empty slots are masked when commands that do not involve keys are sent.
6.5.5 HIGH 2021-03-05 Fixed issue
6.5.4 HIGH 2021-02-07 Fixed issue
  • Excessively slow response receival of clients may cause memory leaks.
6.5.3 HIGH 2021-01-21 New feature
  • Variables are supported in the indexes of keys from Lua scripts.
Fixed issue
  • Memory leaks occur on cluster instances that have more than 32 data shards when the MULTI or BLOCK command is run. For more information, see Cluster master-replica instances.
6.5.2 HIGH 2021-01-19 Fixed issue
  • The 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 log entries related to commands that involve multiple keys are recorded in slow logs.
6.5.0 HIGH 2020-12-24 Fixed issue
  • The system may not respond when the GIS.GETALL command is run. For more information about this command, see TairGIS commands.

6.4.x

Minor version number Update level Release date Type Description
6.4.10 MEDIUM 2020-12-01 Feature optimization
  • The prompt that is displayed when a wrong password is entered is optimized to facilitate your understanding.
6.4.9 HIGH 2020-11-06 Fixed issue
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 max_session_processing parameter cannot be dynamically configured. 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 servers is optimized.
6.4.6 HIGH 2020-09-30 Fixed issue
  • Timeout issues may occur due to uninitialized node roles when the SLOWLOG command is run for standard or cluster instances due to.
  • Connections to ApsaraDB for Memcache instances of specified specifications cannot be established by using Data Management (DMS). For more information, see What is ApsaraDB for Memcache? and Overview.
  • The system does not respond because keys are not specified when __keyspace@0__ is subscribed.
6.4.5 LOW 2020-09-27 New feature
  • Some internal commands are supported.
6.4.3 HIGH 2020-09-25 Feature optimization
  • The special implementation of the pipeline in 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 system incorrectly records slow logs by using the BZPOPMIN and XREAD commands. For more information, see Query slow logs.
6.4.2 HIGH 2020-09-09 Fixed issue
  • By default, idle connections are closed after 1 minute.
6.4.1 MEDIUM 2020-08-25 New feature
  • The timeout configurations are supported. Idle connections can be automatically closed.
  • Statistics of slow logs on read replicas can be collected. This indicates that the SLOWLOG command is sent to all master and read-only nodes. 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 rapid increase of memory usage due to memory fragmentation.
  • The capabilities of proxy servers to handle new connections are improved.
6.4.0 HIGH 2020-08-18 Fixed issue
  • The system does not respond when you use the stat() function before a Configserver node completes configurations.

6.3.x

Minor version number 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 help you identify slow logs. For more information, see Query slow logs.
Feature optimization
  • The capabilities of proxy servers to handle short-lived connections are improved.
6.3.8 HIGH 2020-07-24 Fixed issue
  • Memory usage increases because the vector::clear() function does not take effect.
6.3.7 HIGH

2020-07-13

Fixed issue
  • After SSL encryption is enabled, the system may not respond when a connection is established.
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 to collect statistics of IP addresses, keys, and commands. For more information, see Supported parameters.
Fixed issue
  • After a connection is released, the system may not respond when the CheckExceedLimitAndClose command is run.
  • The SSL encryption feature cannot be enabled.
6.3.4 HIGH 2020-05-21 Fixed issue
  • Subsequent requests may not be responded due to empty packages such as \r\n.