You can fine-tune and customize parameters for your ApsaraDB for Redis instances based on your business scenarios to improve the performance and security of the instances. This topic describes the parameters that are supported in different engine versions and architectures.
Precautions
If the
Parameter is not supported for current versionerror is returned when you configure parameters, update the minor version of your instance. For more information, see Update the minor version of an instance.After you submit the modifications for specific parameters, your instance is automatically restarted. During the restart, the instance encounters transient connections that last for a few seconds. On the page for modifying parameters, the Restart and Take Effect column indicates whether the instance must be restarted for the modifications to take effect. For more information, see Configure instance parameters.
This topic describes the parameters that are supported by ApsaraDB for Redis Community Edition instances. For information about the parameters that are supported by ApsaraDB for Redis Enhanced Edition (Tair) instances, including DRAM-based, persistent memory-optimized, and ESSD-based instances, see Parameters that can be configured for Tair instances.
Supported parameters and descriptions
The following items describe the symbols that are used in the tables of this topic:
The ️️️️✔️ symbol indicates that the major version or instance architecture supports the parameter.
The symbol indicates that the major version or instance architecture does not support the parameter.
To ensure the stability of ApsaraDB for Redis instances, only specific parameters can be set. The parameters that are not described in this topic cannot be set.
For more information about instance architectures, see Standard master-replica instances, Cluster master-replica instances, and Read/write splitting instances.
Parameter | Description | Instance major version and architecture | ||||
Redis 7.0 | Redis 6.0 | Redis 5.0 | Redis 4.0 | Redis 2.8 | ||
#no_loose_check-whitelist-always | Specifies whether to check that the IP address of a client is added to a whitelist of your ApsaraDB for Redis instance after password-free access is enabled for the instance. The client is deployed in the same virtual private cloud (VPC) as the instance. Valid values:
Note This parameter is available only for local disk-based instances. | ❌ | ❌ | Standard ️✔️ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | ❌ |
#no_loose_disabled-commands | The disabled commands. You can use this parameter to disable the commands that may have high risks or high time complexity based on your business requirements, such as FLUSHALL, FLUSHDB, KEYS, HGETALL, EVAL, EVALSHA, and SCRIPT. Note
| Standard ️✔️ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️✔️ Read/write splitting ️✔️ |
sentinel_compat_enable | Specifies whether to enable the Sentinel-compatible mode for cluster instances in proxy mode or read/write splitting instances. Valid values:
| Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | ❌ |
#no_loose_sentinel-enabled | Specifies whether to enable the Sentinel-compatible mode for standard instances or cluster instances in direct connection mode. Valid values:
| Standard ️✔️ Cluster ️️️️️️✔️ Read/write splitting ❌ | Standard ️✔️ Cluster ️️️️️️✔️ Read/write splitting ❌ | Standard ️✔️ Cluster ️️️️️️✔️ Read/write splitting ❌ | Standard ️✔️ Cluster ️️️️️️✔️ Read/write splitting ❌ | ❌ |
#no_loose_ssl-enabled | Specifies whether to enable SSL encryption. Valid values:
Note This parameter is available only for local disk-based instances. | ❌ | ❌ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ |
#no_loose_statistics-cmds | This parameter is related to the observability of ApsaraDB for Redis. After you specify this parameter for an instance, you must also enable the audit log feature for the instance. Audit logs are collected at an interval of 5 seconds.
Note
| ❌ | ❌ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ |
#no_loose_statistics-ip-enable | ❌ | ❌ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | |
#no_loose_statistics-keys | ❌ | ❌ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | |
#no_loose_tls-min-version | The earliest Transport Layer Security (TLS) version supported by the instance. Valid values:
| Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ |
cluster_compat_enable | Specifies whether to enable the support for the syntax of native Redis clusters for cluster instances in proxy mode or read/write splitting instances. Valid values:
| Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ |
max_session_processing | The maximum number of pending requests that are allowed per connection. If a proxy node forwards requests from a client to a data node but does not receive a response from the data node, these requests are pending. This parameter is used to limit pending requests that are caused by capability differences between the frontend and backend of proxy nodes. This prevents an increase in memory usage. | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ |
ptod_enabled | Specifies whether to pass through client IP addresses to data nodes by using proxy nodes. Valid values:
Note This parameter is irrelevant to standard instances or cluster instances in direct connection mode. | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | ❌ |
readonly_lua_route_ronode_enable | Specifies whether to enable Lua scripting on read replicas. Valid values:
| Standard ❌ Cluster ️️️️️❌️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️❌️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️❌️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️❌️ Read/write splitting ️✔️ | ❌ |
read_request_only_ronode_whenrwsplit_enable | Specifies whether to enable unidirectional forwarding for requests from accounts that have read-only permissions. Valid values:
| Standard ❌ Cluster ️️️️️❌️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️❌️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️❌️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️❌️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️❌️ Read/write splitting ️✔️ |
rt_threshold_ms | The threshold for logging slow queries of a proxy node. Unit: milliseconds. If the proxy node processes a request for a period of time longer than the specified threshold, the request is recorded in a slow log. Note This period of time starts when the proxy node sends a request to a data node and ends when the proxy node receives the response. | Standard ❌ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ |
script_check_enable | Specifies whether to check that the keys used in Lua scripts are mapped to the same slot for cluster instances in proxy mode or read/write splitting instances. For more information, see Additional checks on Lua scripts in proxy mode. Valid values:
| Standard ❌ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ |
transfer_subscrible_to_psubscrible_enable | Specifies whether to enable the feature of converting SUBSCRIBE to PSUBSCRIBE. Valid values:
| Standard ❌ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ❌ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | ❌ |
appendfsync | The frequency at which to perform the fsync operation for append-only file (AOF) persistence. The default value is everysec and cannot be changed. This parameter is available only if the appendonly parameter is set to yes. | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ |
appendonly | Specifies whether to enable AOF persistence for master nodes. Valid values:
| Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ |
client-output-buffer-limit pubsub | The output buffer limits of publisher and subscriber clients. The clients are disconnected when the specified limits are reached. Specify this parameter in the following format:
| Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ |
dynamic-hz | Specifies whether to enable dynamic frequency control for background tasks. Valid values:
| Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | ❌ | ❌ |
| hash-max-ziplist-entries and hash-max-ziplist-value are available for Redis 6.0 and earlier. Ziplist encoding is used only if a hash meets the following conditions:
| ❌ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ |
| hash-max-listpack-entries and hash-max-listpack-value are available starting from Redis 7.0. Ziplist (listpack) encoding is used only if a hash meets the following conditions:
| Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | ❌ | ❌ | ❌ | ❌ |
hz | Specifies how frequently tasks are performed in the background for the ApsaraDB for Redis instance. For example, you can specify how frequently tasks are performed to evict expired keys. Valid values: 1 to 500. The default value is 10, which specifies that each task is performed 10 times per second. Note A larger value results in higher CPU consumption of the ApsaraDB for Redis instance but allows the system to delete expired keys more frequently and close timeout connections more precisely. We recommend that you specify a value less than or equal to 100. | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ |
latency-tracking | Specifies whether to enable tracking of per-command latencies. Valid values:
Note This parameter is available only for Redis 7.0. | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | ❌ | ❌ | ❌ | ❌ |
lazyfree-lazy-eviction | Specifies whether to enable the eviction feature based on the lazyfree mechanism. Valid values:
| Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | ❌ |
lazyfree-lazy-expire | Specifies whether to delete expired keys based on the lazyfree mechanism. Valid values:
| Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | ❌ |
lazyfree-lazy-server-del | Specifies whether to asynchronously delete data based on the lazyfree mechanism for an implicit DEL operation. Valid values:
| Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | ❌ |
lazyfree-lazy-user-del | Specifies whether to asynchronously delete data based on the lazyfree mechanism when a user runs the DEL command. Valid values:
| Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | ❌ | ❌ | ❌ |
lazyfree-lazy-user-flush | Specifies whether to control the FLUSHDB, FLUSHALL, SCRIPT FLUSH, and FUNCTION FLUSH commands to asynchronously delete data based on the lazyfree mechanism. Valid values:
Note This parameter is available only for Redis 7.0. | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | ❌ | ❌ | ❌ | ❌ |
list-compress-depth | The number of nodes that are not compressed at both ends of a list. Valid values: 0 to 65535.
| Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | ❌ |
list-max-ziplist-entries | The maximum number of elements that can be stored in a list and the maximum size of each element in the list. Ziplist encoding is used only if a list meets both of the following conditions:
| ❌ | ❌ | ❌ | ❌ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ |
list-max-ziplist-value | ||||||
| list-max-ziplist-size is available for Redis 6.0 and earlier, whereas list-max-listpack-size is available starting from Redis 7.0.
| Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | ❌ |
maxmemory-policy | The policy used to evict keys if memory is exhausted. If the memory usage of your ApsaraDB for Redis instance reaches the value of Maxmemory, data eviction is triggered. You can choose a data eviction policy based on your needs. Valid values: Note
| Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ |
maxmemory-eviction-tenacity | The Eviction factor that is used to set the latency of each data eviction. Valid values: 0 to 100. Default value: 10.
Note This parameter is available only for Redis 7.0. | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | ❌ | ❌ | ❌ | ❌ |
active-expire-effort | The Expire factor that is used to set the latency of each deletion of expired keys. Valid values: 1 to 10. Default value: 1. The larger the value, the faster expired keys are deleted and the more CPU resources are used. | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | ❌ | ❌ | ❌ |
notify-keyspace-events | The types of events of which the server can notify clients. The value of this parameter is a combination of the following characters. This parameter setting applies to all databases in the instance. These notifications consume CPU resources. For more information, see Redis keyspace notifications.
Important The specified value must include at least K or E. Otherwise, no notifications are sent. For example, if you want to be notified of expiration events, set this parameter to | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ |
set-max-intset-entries | The maximum number of data entries for which a set supports intset encoding. Intset encoding is used if a set meets the following conditions:
| Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ |
slowlog-log-slower-than | The threshold for logging slow queries. When an operation is executed for a period of time that exceeds the specified threshold, the operation is logged. Unit: microseconds. Valid values: 10000 to 10000000. Default value: 20000 (20 milliseconds). | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ |
slowlog-max-len | The maximum number of entries that can be stored in a slow log. Valid values: 100 to 10000. Default value: 1024. | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ |
stream-node-max-bytes | The maximum amount of memory that each macro node in a stream can occupy. Valid values: 0 to 999999999999999. Unit: bytes. Note A value of 0 indicates that the amount of memory that each macro node can consume is unlimited. | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | ❌ | ❌ |
stream-node-max-entries | The maximum number of entries that can be stored on each macro node in a stream. Valid values: 0 to 999999999999999. Note A value of 0 indicates that the number of entries that can be stored on each macro node is unlimited. | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️✔️ Read/write splitting ️✔️ | ❌ | ❌ |
tracking-table-max-keys | The maximum number of keys that can be stored in the tracking table. Valid values: 0 to 1000000000. Default value: 1000000. Note This parameter is available only for Redis 7.0. | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | ❌ | ❌ | ❌ | ❌ |
timeout | The timeout period. The system closes a connection to a client for the ApsaraDB for Redis instance if the connection remains idle for the specified period of time. Valid values: 0 to 100000. Unit: seconds. The default value is 0, which indicates that no timeout periods are specified. | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | ❌ |
| zset-max-ziplist-entries and zset-max-ziplist-value are available for Redis 6.0 and earlier. Ziplist encoding is used only if a sorted set meets the following conditions:
| ❌ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ |
| zset-max-listpack-entries and zset-max-listpack-value are available starting from Redis 7.0. Listpack encoding is used only if a sorted set meets the following conditions:
| Standard ️✔️ Cluster ️️️️️️️️️️️️️️️️✔️️️️️ Read/write splitting ️✔️ | ❌ | ❌ | ❌ | ❌ |