Supported parameters - ApsaraDB for Redis - Alibaba Cloud Documentation Center

ApsaraDB for Redis allows you to modify specific instance parameters. The instance parameters that can be modified vary with the engine version and instance architecture. This topic describes how to modify instance parameters.

Precautions

If the Parameter is not supported for current version error appears when you configure parameters, update the minor version of your instance. For more information, see Update the minor version.
After you submit the modifications for specific parameters, your instance is automatically restarted. The instance experiences transient connections that last for a few seconds during the restart. On the page for modifying parameters in the Tair console, the Restart and Take Effect column indicates whether the instance must be restarted for the modification to take effect. For more information, see Modify the values of parameters for an instance.

Important This topic is applicable only to ApsaraDB for Redis Community Edition instances. For information about the parameters supported for ApsaraDB for Redis Enhanced Edition (Tair) instances including DRAM-based instances, Persistent memory-optimized instances, and ESSD-based instances, see Supported parameters.

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.

Note

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	Major version and instance architecture
Parameter	Description	Redis 6.0	Redis 5.0	Redis 4.0	Redis 2.8
#no_loose_audit-read-enabled	Specifies whether to enable read request audit. After you enable this feature, you can view information about read requests in the audit logs. For more information about audit logs, see Enable the new audit log feature. Default value: no. Valid values: yes: enables read request audit. no: does not enable read request audit. Note This parameter is unavailable for instances that use cloud disks.	❌	Standard❌ Cluster✔️ Read/write splitting✔️	Standard ❌ Cluster ✔️ Read/write splitting ️️️✔️	Standard ❌ Cluster ✔️ Read/write splitting ️️️️️✔️
#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 VPC as the instance. Default value: no. Valid values: yes: checks whether the IP address of a client is added to a whitelist of the instance. After you enable password-free access for the instance, you must also add the IP address of a client that is deployed in the same VPC as the instance to a whitelist of the instance before the client can connect to the instance. If the `(error) ERR illegal address` error is returned, the whitelist is configured in an invalid way. no: does not check whether the IP address of a client is added to a whitelist of the instance. After you enable password-free access for the instance, you can connect a client that is deployed in the same VPC as the instance to the instance without adding the IP address of the client to a whitelist of the instance. Note This parameter is unavailable for instances that use cloud disks.	❌	Standard ️️️✔️ Cluster ️️️✔️ Read/write splitting ️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️✔️ Read/write splitting ️️️️✔️	❌
#no_loose_disabled-commands	Disables 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 Specify commands in lowercase letters and separate the commands with commas (,). Even if you disable the FLUSHALL command, the Clear Data feature can still be used in the Tair console. To ensure stable instance performance for ApsaraDB for Redis, specific commands cannot be disabled, such as SAVE and SHUTDOWN. For more information, see High-risk commands that cannot be disabled.	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 read/write splitting instances and cluster instances in proxy mode. Default value: 0. Valid values: 1: enables the Sentinel-compatible mode. 0: disables the Sentinel-compatible mode.	Cluster ✔️ Read/write splitting ✔️	Cluster ✔️ Read/write splitting ✔️	Cluster ✔️ Read/write splitting ✔️	❌
#no_loose_sentinel-enabled	Specifies whether to enable the Sentinel-compatible mode for standard instances and cluster instances in direct connection mode. Default value: no. Valid values: yes: enables the Sentinel-compatible mode. no: disables the Sentinel-compatible mode.	Standard ️️️✔️ Cluster ️️️✔️	Standard ️️️✔️ Cluster ️️️✔️	Standard ️️️✔️ Cluster ️️️✔️	❌
#no_loose_ssl-enabled	Specifies whether to enable SSL encryption. Default value: no. Valid values: yes: enables SSL encryption. no: disables SSL encryption. Note This parameter is unavailable for instances that use cloud disks.	❌	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. #no_loose_statistics-cmds: specifies the commands whose statistics you want to collect. The source IP addresses from which the commands are issued and the frequencies at which the commands are run are collected. This parameter is empty by default, which indicates that no statistics are collected. Separate multiple commands with commas (,). #no_loose_statistics-ip-enable: specifies whether to enable the collection of statistics about IP addresses or whether to record IP addresses of established connections. Default value: no. Valid values: yes and no. #no_loose_statistics-keys: specifies the keys whose statistics you want to collect. The source IP addresses from which and the frequencies at which these keys are queried or updated are collected. This parameter is empty by default, which indicates that no statistics are collected. Separate multiple keys with commas (,). Note To prevent performance degradation, we recommend that you do not specify an excessive number of commands for the #no_loose_statistics-cmds parameter and an excessive number of keys for the #no_loose_statistics-keys parameter. In addition, make sure that these parameters are enabled only when you want to troubleshoot issues or perform O&M tasks. You can download audit logs in the Log Service console and use the keywords described in the following section to find the logs that you want to view. For more information about how to download audit logs, see Enable the new audit log feature. A type value of 7: indicates the queries per second (QPS) of IP addresses. A type value of 8: indicates the connection information of IP addresses. A type value of 9: indicates the statistics of keys. A type value of 10: indicates the statistics of commands.	❌	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	Specifies the earliest Transport Layer Security (TLS) version supported by the instance. Default value: TLSv1. Valid values: TLSv1 Tlsv1.1 TLSv1.2	❌	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 read/write splitting instances and cluster instances in proxy mode. Default value: 1. Valid values: 0: disables support for the syntax of native Redis clusters. 1: enables support for the syntax of native Redis clusters.	❌	Standard ❌ Cluster ✔️ Read/write splitting ️️️✔️	Standard ❌ Cluster ✔️ Read/write splitting ️️️✔️	Standard ❌ Cluster ✔️ Read/write splitting ️️️️✔️
max_session_processing	Specifies 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 the number of 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 ️️️️✔️
ptod_enabled	Specifies whether to pass through client IP addresses to data nodes by using proxy nodes. Default value: 0. Valid values: 0: does not pass through client IP addresses to data nodes. 1: passes through client IP addresses to data nodes. Note This parameter is irrelevant to instances that use the standard architecture or instances that use the cluster architecture and have the direct connection mode enabled.	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. Default value: 0. Valid values: 0: disables Lua scripting. Lua scripts are processed by master nodes instead of read replicas. 1: enables Lua scripting. Lua scripts that include only read requests are forwarded to read replicas.	❌	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. Default value: 0. Valid values: 0: disables unidirectional forwarding. Requests from accounts that have read-only permissions are forwarded based on weights to all nodes including master nodes. 1: enables unidirectional forwarding. Requests from accounts that have read-only permissions are forwarded only to read replicas.	❌	Standard ❌ Cluster ❌ Read/write splitting ️️️✔️	Standard ❌ Cluster ❌ Read/write splitting ️️️✔️	Standard ❌ Cluster ❌ Read/write splitting ️️️️✔️
rt_threshold_ms	Specifies the threshold to log 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 ️️✔️
script_check_enable	Specifies whether to check that the keys used in Lua scripts are mapped to the same slot. Default value: 1. Valid values: 0: does not check whether the keys are mapped to the same slot. 1: checks whether the keys are mapped to the same slot.	❌	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. Default value: 0. Valid values: 0: disables this feature. Proxy nodes cannot convert SUBSCRIBE to PSUBSCRIBE. 1: enables this feature. Proxy nodes can convert SUBSCRIBE to PSUBSCRIBE. Note If you use Pub/Sub commands in Lua scripts and the channel to which you have subscribed cannot receive messages, you can enable this feature to fix this issue.	❌	Standard ❌ Cluster ️️️️✔️ Read/write splitting ️️✔️	Standard ❌ Cluster ️️️️✔️ Read/write splitting ️️✔️	❌
appendfsync	Specifies the frequency to perform fsync operations of 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 ️️✔️
appendonly	Specifies whether to enable append-only file (AOF) persistence for master nodes. Default value: yes. Valid values: yes: enables AOF persistence. no: disables AOF persistence. Note By default, data persistence by using Redis Database (RDB) snapshots is performed once a day. For more information, see Automatic or manual backup.	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	Specifies the output buffer limits of publisher and subscriber clients. The clients are disconnected when the specified limits are reached. Specify a value for this parameter in the following format: `<hard limit> <soft limit> <soft seconds>`. Default value: 33554432 8388608 60. `<hard limit>`: the hard limit. A client is disconnected if the output buffer of the client is greater than or equal to the hard limit value. The hard limit value is measured in bytes. `<soft limit>`: the soft limit. `<soft seconds>`: the maximum number of seconds for which the soft limit is reached or exceeded. A client is disconnected if its output buffer remains greater than or equal to the soft limit value for a period of time that is longer than or equal to the soft seconds value. The soft limit value is measured in bytes. The soft seconds value is measured in seconds.	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. Default value: yes. Valid values: yes: enables dynamic frequency control for background tasks. no: disables dynamic frequency control for background tasks.	Standard ️️️️️️️✔️ Cluster ️️✔️ Read/write splitting ✔️	Standard ️️️️️️️✔️ Cluster ❌ Read/write splitting ❌	❌	❌
hash-max-ziplist-entries	Specifies the maximum number of key-value pairs stored in a hash. Ziplist encoding is used only if both of the following conditions are met: The keys and values of key-value pairs stored in the hash are all smaller than the value of the hash-max-ziplist-value parameter. The keys and values are measured in bytes. The number of key-value pairs stored in the hash is smaller than the value of the hash-max-ziplist-entries parameter.	Standard ️️️️️️️✔️ Cluster ️️✔️ Read/write splitting ✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️️️️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️️️️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️✔️
hash-max-ziplist-value	Specifies the maximum size of the keys and values of key-value pairs stored in a hash. Ziplist encoding is used only if both of the following conditions are met: The keys and values of key-value pairs stored in the hash are all smaller than the value of the hash-max-ziplist-value parameter. The keys and values are measured in bytes. The number of key-value pairs stored in the hash is smaller than the value of the hash-max-ziplist-entries parameter.	Standard ️️️️️️️✔️ Cluster ️️✔️ Read/write splitting ✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️️️️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️️️️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️✔️
hz	Specifies how frequently tasks are performed in the background. 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 greater value results in higher CPU utilization but allows ApsaraDB for Redis 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 ️️✔️
lazyfree-lazy-eviction	Specifies whether to enable the eviction feature based on the lazyfree mechanism. Default value: no. Valid values: yes: enables the eviction feature. no: disables the eviction feature.	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. Default value: yes. Valid values: yes: deletes expired keys. no: does not delete expired keys.	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. Default value: yes. Valid values: yes: asynchronously deletes data. no: does not asynchronously delete data.	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. Default value: yes. Valid values: yes: asynchronously deletes data. no: does not asynchronously delete data.	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ✔️	❌	❌	❌
list-compress-depth	Specifies the number of nodes that are not compressed at both ends of a list. Default value: 0. Valid values: 0 to 65535. 0: does not compress nodes of a list. A value in the range of 1 to 65535: does not compress the specified number of nodes at both ends of a list but compresses in-between nodes.	Standard ️️️️️️️✔️ Cluster ️️✔️ Read/write splitting ✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️️️️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️✔️	❌
list-max-ziplist-entries	Specifies the maximum number of elements stored in a list. Ziplist encoding is used only if both of the following conditions are met: The elements stored in the list are all smaller than the value of the list-max-ziplist-value parameter. The elements are measured in bytes. The number of elements stored in the list is smaller than the value of the list-max-ziplist-entries parameter.	❌	❌	❌	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️✔️
list-max-ziplist-value	Specifies the maximum size of the elements stored in a list. Ziplist encoding is used only if both of the following conditions are met: The elements stored in the list are all smaller than the value of the list-max-ziplist-value parameter. The elements are measured in bytes. The number of elements stored in the list is smaller than the value of the list-max-ziplist-entries parameter.	❌	❌	❌	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️✔️
list-max-ziplist-size	Specifies the maximum size of each ziplist in a quicklist. A positive number indicates the maximum number of elements in each ziplist of a quicklist. For example, if you set this parameter to 5, each ziplist of a quicklist can contain a maximum of five elements. A negative value indicates the maximum number of bytes in each ziplist of a quicklist. Default value: -2. Valid values: -5: specifies that each ziplist of a quicklist cannot exceed 64 KB. -4: specifies that each ziplist of a quicklist cannot exceed 32 KB. -3: specifies that each ziplist of a quicklist cannot exceed 16 KB. -2: specifies that each ziplist of a quicklist cannot exceed 8 KB. -1: specifies that each ziplist of a quicklist cannot exceed 4 KB.	Standard ️️️️️️️✔️ Cluster ️️✔️ Read/write splitting ✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️️️️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️✔️	❌
maxmemory-policy	Specifies 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 By default, Maxmemory is set to the storage capacity of the instance class of the ApsaraDB for Redis instance and cannot be changed. For example, if the storage capacity of the instance class is 2 GB, the value of Maxmemory is 2 GB. LRU indicates least recently used. LFU indicates least frequently used. LRU, LFU, and time-to-live (TTL) policies are implemented by using approximation and randomized algorithms. Valid values: volatile-lru: evicts the LRU keys among keys that have a configured TTL. allkeys-lru: evicts the LRU keys among all keys. volatile-lfu: evicts LFU keys among keys that have a configured TTL. allkeys-lfu: evicts LFU keys among all keys. volatile-random: randomly evicts keys among keys that have a configured TTL. allkeys-random: randomly evicts keys among all keys. volatile-ttl: evicts the key that has the shortest TTL among keys that have a configured TTL. noeviction: does not evict keys, but returns error messages for write operations.	Standard ️️️️️️️✔️ Cluster ️️✔️ Read/write splitting ✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️️️️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️️️️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️✔️
notify-keyspace-events	Specifies 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. K: keyspace events. All notifications are prefixed with `__keyspace@<db>__`. E: keyevent events. All notifications are prefixed with `__keyevent@<db>__`. g: generic events that are not related to specific commands, such as DEL, EXPIRE, and RENAME. $: events of string commands. Clients are notified of operations to create, modify, and delete strings. l: events of list commands. s: events of set commands. h: events of hash commands. z: events of sorted set commands. x: expiration events. Clients may be notified when an expired key is deleted instead of when a key expires. e: eviction events. Clients are notified when a key is evicted based on maxmemory policies. A: listens to all the preceding event types. This parameter is the alias for the g$lshzxe parameter. Example: AKE. 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 `Ex`. If you run the `PSUBSCRIBE __keyevent@0__*` command on your client after you specify this parameter, you are notified of the keyevent events of database 0.	Standard ️️️️️️️✔️ Cluster ️️✔️ Read/write splitting ✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️️️️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️️️️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️✔️
set-max-intset-entries	Specifies the maximum number of data entries for which a set supports intset encoding. A set uses intset encoding when the following conditions are met: All data entries in the set are strings. The set contains only radix-10 integers in the range of 64-bit signed integers.	Standard ️️️️️️️✔️ Cluster ️️✔️ Read/write splitting ✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️️️️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️️️️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️✔️
slowlog-log-slower-than	Specifies the threshold to log 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.	Standard ️️️️️️️✔️ Cluster ️️✔️ Read/write splitting ✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️️️️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️️️️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️✔️
slowlog-max-len	Specifies 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 ️️✔️
stream-node-max-bytes	Specifies 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 no limits exist.	Standard ️️️️️️️✔️ Cluster ️️✔️ Read/write splitting ✔️	Standard ️️️️️️️✔️ Cluster ❌ Read/write splitting ❌	❌	❌
stream-node-max-entries	Specifies 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 no limits exist.	Standard ️️️️️️️✔️ Cluster ️️✔️ Read/write splitting ✔️	Standard ️️️️️️️✔️ Cluster ❌ Read/write splitting ❌	❌	❌
timeout	Specifies a timeout period. The system closes a connection to a client if the connection remains idle for the specified period of time. Valid values: 0 to 100000. Unit: seconds. Note A value of 0 indicates that no timeout periods are specified.	Standard ️️️️️️️✔️ Cluster ️️✔️ Read/write splitting ✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️️️️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️✔️	❌
zset-max-ziplist-entries	Specify the maximum number of key-value pairs stored in a sorted set and the maximum size of the keys and values of key-value pairs stored in the sorted set. Ziplist encoding is used only if the following conditions are met: The keys and values of key-value pairs stored in the sorted set are all smaller than the value of the hash-max-ziplist-value parameter. The keys and values are measured in bytes. The number of key-value pairs stored in the sorted set is smaller than the value of the zset-max-ziplist-entries parameter.	Standard ️️️️️️️✔️ Cluster ️️✔️ Read/write splitting ✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️️️️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️️️️️️️✔️	Standard ️️️️️️️✔️ Cluster ️️️️️️️️✔️ Read/write splitting ️️✔️
zset-max-ziplist-value		Standard ️️️️️️️✔️ Cluster ️️✔️ Read/write splitting ✔️