Release Notes
Announcements
Parameter | Note | Supported Version |
active-expire-effort | Adjusting the upper limit of CPU usage during active expiration of keys. Value range: 1–10. Default value: 1. Upper limit of CPU usage = 25% + (n-1) x 2%. The default value of 1 corresponds to a CPU usage limit of 25%. The maximum value of 10 corresponds to a CPU usage limit of 43%. | Redis 6.2 or later versions ValKey 8.0 |
auto-failback | When deploying instances in multiple availability zones, this parameter specifies whether the primary node will automatically switch back to the primary node group (cluster) after fault recovery. | Redis 4.0 or later versions ValKey 8.0 |
disable-command-list | Set disabled commands. Users can close certain commands with high time complexity or high risk according to actual business needs. Disabled commands will not be allowed to run in this instance. Multiple commands can be configured, such as "flushdb,keys". | Redis 2.8 or later versions ValKey 8.0 |
hz
| Set the execution frequency. | Redis 2.8 or later versions ValKey 8.0 |
maxmemory-policy | Set the eviction policy for data when the memory cache is full. You can choose from the following policies: volatile-lru: For keys with TTL expiration time set, use the LRU algorithm to evict and delete, that is, prioritize evicting the least recently used keys among those with (TTL) set. allkeys-lru: For all keys, use the LRU algorithm to evict and delete, that is, regardless of whether the timeout attribute is set, prioritize evicting the least recently used keys until sufficient space is freed up. volatile-random: Randomly evict and delete keys with TTL expiration time set. allkeys-random: Evict and delete all keys randomly. volatile-ttl: For keys with TTL expiration time set, prioritize evicting keys with smaller TTL values among those with expiration time set. noeviction: Do not evict and delete any keys; reject all write operations and return an error message during write operations. volatile-lfu: Prioritize evicting the LFU keys among those with the TTL set. allkeys-lfu: Prioritize evicting the LFU keys. Different from volatile-lfu, the allkeys-lfu policy will evict all keys, not just those with the TTL set. Where LRU (Least Recently Used) stands for Least Recently Used; TTL (Time To Live) means setting an expiration time; LFU (Least Frequently Used) stands for Least Frequently Used. For detailed information, see Basic Usage Guidelines. | Redis 2.8 or later versions ValKey 8.0 Memcached 1.6 |
UserPasswordSeparate | Specify the password connector for the custom account. Note: If Current Runtime Parameter Value indicates that the current proxy version does not support modifying the UserPasswordSeparate parameter, please upgrade the proxy version according to the interface prompts. | Redis 4.0 or later versions ValKey 8.0 |
cluster-node-timeout | Set the cluster node timeout, which is the time in milliseconds that a node in the cluster is unreachable before the node is considered in a failed status. | Redis 4.0 or later versions ValKey 8.0 |
rehash-maintenance-time | Set whether to allow rehash operations during the maintenance window. Note: If the interface indicates that the Distributed Cache minor version does not support modifying the rehash-maintenance-time parameter, please upgrade the minor version. no: The parameter defaults to no, meaning that the feature is not enabled, and the native Redis rehash solution is used, triggering rehash when the load factor reaches the preset threshold. yes: enable Tencent's self-developed rehash enhanced feature to minimize or reduce performance fluctuations during the operation of Distributed Cache. When the hash table's load factor is less than 1.618, perform gradual rehash during the maintenance window to avoid potential performance impacts. When the hash table's load factor exceeds 1.618, the system automatically triggers a full rehash to ensure the efficiency and stability of the data structures. | Redis 4.0 or later versions ValKey 8.0 |
hash-max-ziplist-entries | A hash object uses ziplist encoding when it satisfies both of the following conditions: The string lengths of keys and values of all key-value pairs stored in the hash object are less than the value of hash-max-ziplist-value. The quantity of key-value pairs stored in the hash object is less than the value of hash-max-ziplist-entries. | Redis 2.8 or later versions ValKey 8.0 |
hash-max-ziplist-value | A hash object uses ziplist encoding when it satisfies both of the following conditions: The string lengths of keys and values of all key-value pairs stored in the hash object are less than the value of hash-max-ziplist-value. The quantity of key-value pairs stored in the hash object is less than the value of hash-max-ziplist-entries. | Redis 2.8 or later versions ValKey 8.0 |
lazyfree-lazy-eviction
| This parameter controls whether Distributed Cache performs (Lazy Free) and (Lazy Eviction) during memory reclamation. Lazy Free: When Distributed Cache needs to delete a key-value pair, it does not immediately remove it from memory. Instead, it marks the key-value pair as "to be deleted" and waits until the next access to delete it. The pair is stored in an expiration queue, and expired keys are cleaned up at the frequency set by HZ. Lazy Eviction: When Distributed Cache needs to free up memory space, it does not immediately release memory. Instead, it marks certain key-value pairs as "to be evicted" and stores them in an expiration queue. Expired keys are then cleaned up at the frequency set by HZ. This approach reduces the overhead of memory reclamation but results in higher memory usage. The values for this parameter are as follows. no: Indicates that lazy free and lazy eviction are not used. Distributed Cache immediately deletes key-value pairs or releases memory space during memory reclamation. yes: Indicates that lazy free and lazy eviction are used. | Redis 2.8 or later versions ValKey 8.0 |
lazyfree-lazy-expire | This parameter is used to control whether Distributed Cache performs (Lazy Free) when expired key deletion is executed. no: Indicates that lazy free is not used. Distributed Cache immediately deletes key-value pairs when performing expired key deletion. yes: Indicates that lazy free is used. Distributed Cache marks certain Key-value pairs as "to be deleted" during expired Key deletion, stores them in an expiration queue, and cleans up expired keys at the frequency set by HZ. | Redis 4.0 or later versions ValKey 8.0 |
lazyfree-lazy-server-del | This parameter controls the lazy free behavior of Distributed Cache when the DEL command is executed to delete key-value pairs. no: Indicates that lazy free is not used. Distributed Cache immediately deletes key-value pairs when executing the DEL command to delete key-value pairs. yes: Indicates that lazy free is used. Distributed Cache marks certain key-value pairs as "to be deleted" when the DEL command is executed to delete key-value pairs, stores them in an expiration queue, and cleans up expired keys at the frequency set by HZ. | Redis 4.0 or later versions ValKey 8.0 |
lazyfree-lazy-user-del | Users or applications can enable or disable lazy free (Lazy Free) when executing the DEL command to delete one or more key-value pairs in Distributed Cache. no: The DEL command directly deletes key-value pairs from memory without performing lazy free. yes: When the DEL command is executed, lazy free is performed first. Distributed Cache immediately returns OK and delegates the deletion task to a background thread for asynchronous processing. | Redis 4.0 or later versions ValKey 8.0 |
lazyfree-lazy-user-flush | When users or applications execute FLUSHDB (flush the current database) or FLUSHALL (flush all databases), lazy free (Lazy Free) can be enabled or disabled. Default value no: Disables lazy free (Lazy Free). Executing the flush command will delete all keys synchronously and blocking. yes: When FLUSHDB or FLUSHALL is executed, Distributed Cache will immediately return OK and delegate the deletion task to a background thread for asynchronous processing. | Redis 4.0 or later versions ValKey 8.0 |
proxy-slowlog-log-slower-than | Set the recording threshold for the Proxy slow log, that is, configure the Proxy to record operations whose execution time exceeds a specified number of milliseconds. | Redis 2.8 or later versions ValKey 8.0 Memcached 1.6 |
replica-lazy-flush | Controls whether to delay releasing resources that are no longer needed during full resynchronization. | Redis 5.0 or later versions ValKey 8.0 |
ScanSlaveNode | When this parameter is enabled, scanning commands (such as SCAN, KEYS, HSCAN, SSCAN, and ZSCAN) will be routed to replica nodes for execution, avoiding a large number of traversal operations from blocking the master node and enhancing overall cluster performance. Valid values: yes: enabled. no: disabled. The default value is no. | Redis 4.0 or later versions ValKey 8.0 |
ClusterNodeAdaptive | When this parameter is enabled, the CLUSTER NODES command will return slot allocation information for each node, allowing the client to perceive the cluster topology. Valid values: yes: slot information included in return results. no: slot information not included in return results. The default value is no. | Redis 4.0 or later versions ValKey 8.0 |
read-local-node-only | When an instance is deployed across multiple AZs, this parameter specifies whether to enable or disable the nearby access feature. | Redis 4.0 or later versions ValKey 8.0 |
sentineauth | This parameter controls whether to bypass the password for Distributed Cache when the sentinel command is used to interact with Redis Sentinel, and automatically use the password corresponding to the sentinelauth parameter specified in the Sentinel configuration file. | Redis 6.2 or later versions ValKey 8.0 |
set-max-intset-entries | When a set object meets both of the following conditions, intset encoding is used: All data in the collection object are strings. They all happen to be integers with a base of 10 in the range of 64-bit signed integers. | Redis 2.8 or later versions ValKey 8.0 |
slowlog-log-slower-than | Set the recording threshold of slow logs, in milliseconds. Operations that have been executed for a period of time longer than this threshold are recorded. | |
timeout | When the client connection idle time reaches the specified value, the connection will be closed. The unit is seconds (s). | |
zset-max-ziplist-entries | A sorted set object uses ziplist encoding when it satisfies both of the following conditions: The number of bytes of the string length of each element of the sorted collection object is less than the specified value of zset-max-ziplist-value. The quantity of elements in the sorted collection object is less than the specified value of zset-max-ziplist-entries. | |
zset-max-ziplist-value | A sorted set object uses ziplist encoding when it satisfies both of the following conditions: The number of bytes of the string length of each element of the sorted collection object is less than the specified value of zset-max-ziplist-value. The quantity of elements in the sorted collection object is less than the specified value of zset-max-ziplist-entries. | |
notify-keyspace-events | The parameter to notify-keyspace-events is an arbitrary combination of the following characters, which defines what types of notifications the server will send. Character: Notifications sent. K: key space notification. All notifications are prefixed with __keyspace@<db>__. E: key event notification. All notifications are prefixed with __keyevent@<db>__. g: Notifications for type-independent general commands such as DEL, EXPIRE, and RENAME. $: String command notifications. l: List command notifications. s: notification of collection commands. h: notification of hash commands. z: notification of sorted collection commands. x: expiration event, which is sent each time an expired key is deleted. e: Eviction event, sent whenever a key is deleted due to the maxmemory policy. A: Alias for the parameter g$lshzxe. Enabling key space notifications will consume CPU computing resources, therefore, this notification is disabled by default. If defining the server to send certain notifications, the input parameters must include K or E; for example, to subscribe to notifications related to eviction events in key events, the parameter should be set to "Ee"; to subscribe to all types of notifications, the parameter should be set to "AKE". | |
list-max-ziplist-entries | A linked list object uses ziplist encoding when it satisfies both of the following conditions: The number of bytes of the string length of each element stored in the linked list object is less than the specified value of list-max-ziplist-value. The number of elements stored in the linked list collection object is less than the specified value of list-max-ziplist-entries. | Redis 2.8 |
list-max-ziplist-value | A linked list object uses ziplist encoding when it satisfies both of the following conditions: The number of bytes of the string length of each element stored in the linked list object is less than the specified value of list-max-ziplist-value. The number of elements stored in the linked list collection object is less than the specified value of list-max-ziplist-entries. | Redis 2.8 |
피드백