Valkey™ settings

For a Yandex Managed Service for Valkey™ cluster, you can set Valkey™ settings.

The label next to the setting name shows which interface can be used to configure this setting: the management console, CLI, API, or Terraform. The All interfaces label means you can use any of the above interfaces.

Depending on the interface you select, the same setting may look differently. For example, Maxmemory policy in the management console is the same as:

• maxmemory_policy in the gRPC API and Terraform
• maxmemoryPolicy in the REST API

DBMS settingsDBMS settings

The following settings are available:

• Activedefrag Management console CLI API

  This setting enables active memory defragmentation in the cluster. It helps reduce memory fragmentation, which can cause low-memory issues. We do not recommend enabling it if you do not have memory fragmentation issues.

  This setting is disabled by default.

  For more information, see this Valkey™ guide.

• Client output buffer limit normal All interfaces

  Limit on the output buffer size for regular clients.

  Valkey™ uses an output buffer to temporarily store сommand-generated data before it reaches the client. If the client is sending new commands faster than Valkey™ can process pending ones, the buffer size increases.

  This setting includes the following parameters:

  • Hard limit: Hard buffer size limit, in bytes. If this limit is crossed, the client connection terminates immediately. The minimum value is 0, i.e., there is no limit. The default value is 0. To define the units of measurement in the management console, use the Hard limit unit setting.
  • Soft limit: Soft buffer size limit, in bytes. The client connection terminates only if this limit is exceeded for the period specified in the Soft seconds setting. The minimum value is 0, i.e., there is no limit. The default value is 0. To define the units of measurement in the management console, use the Soft limit unit setting.
  • Soft seconds: Time (in seconds) during which the soft buffer limit may be exceeded. The minimum value is 0. The default value is 0.

  For more information about this setting, see this Valkey™ guide.

• Client output buffer limit pubsub All interfaces

  Limit on the output buffer size for clients using the Pub/Sub pattern.

  Valkey™ uses an output buffer to temporarily store сommand-generated data before it reaches the client. If the client is sending new commands faster than Valkey™ can process pending ones, the buffer size increases.

  This setting includes the following parameters:

  • Hard limit: Hard buffer size limit, in bytes. If this limit is crossed, the client connection terminates immediately. The minimum value is 0, i.e., there is no limit. The default value is 33554432 (32 MB). To define the units of measurement in the management console, use the Hard limit unit setting.
  • Soft limit: Soft buffer size limit, in bytes. The client connection terminates only if this limit is exceeded for the period specified in the Soft seconds setting. The minimum value is 0, i.e., there is no limit. The default value is 8388608 (8 MB). To define the units of measurement in the management console, use the Soft limit unit setting.
  • Soft seconds: Time (in seconds) during which the soft buffer limit may be exceeded. The minimum value is 0 and the default is 60.

  For more about this setting, see this Valkey™ article.

• Databases All interfaces

  Number of databases.

  Valkey™ uses logical databases isolated from one another. Operations with keys and values in one database do not affect data in other databases. Each database has a unique number, from 0 to Databases − 1.

  The valid values range from 1 to 2147483647. The default value is 16.

  For more information, see this Valkey™ guide.

  Warning

  Updating this parameter will restart all running Valkey™ nodes.

• Lua time limit Management console CLI API

  Maximum Lua script execution time, in milliseconds.

  The valid values range from 0 to 5000. The default value is 5000. If 0, execution time is unlimited.

  Changes do not affect an already running script.

  For more information, see this Valkey™ article.

• Maxmemory percent All interfaces

  Maximum percentage of RAM to allocate for user data on Yandex Managed Service for Valkey™ cluster hosts.

  The valid values range from 1 to 75. The default value is 75.

  Note

  Reducing the maximum percentage decreases the database capacity. This may be helpful if the database experiences OOM Killer issues.

• Maxmemory policy All interfaces

  Memory management mode when low on memory.

  • volatile-lru: Delete keys with expired TTL starting with the least recently used (LRU) one.
  • volatile-lfu: Delete keys with expired TTL starting with the least frequently used (LFU) one.
  • volatile-ttl: Delete keys with expired TTL starting with the shortest TTL one.
  • volatile-random: Delete keys with expired TTL in random order.
  • allkeys-lru: Delete keys regardless of their TTL starting with the least recently used one.
  • allkeys-lfu: Delete keys regardless of their TTL starting with the least frequently used one.
  • allkeys-random: Delete keys regardless of their TTL in any order.
  • noeviction: Do not delete keys and return an error if there is not enough memory to insert data. This is the default setting.

  For more information, see this Valkey™ guide.

• Notify keyspace events All interfaces

  Keyspace event notification setting.

  The setting value is a string of modifiers that manage notification behavior. The default value is an empty string, i.e., notification is disabled.

  For a complete list of modifiers, see this Valkey™ article.

• Slowlog log slower than All interfaces

  Commands running longer than the specified time (in microseconds) are considered slow. Such commands end up in the slow log. If the value is 0, all executed commands are logged.

  The valid values range from -1 (no slow logging) to 9223372036854775807. The default value is 10000.

  For more information, see this Valkey™ guide.

• Slowlog max len All interfaces

  Maximum number of entries in the slow log. When the log reaches this limit, the oldest entries are removed before adding new ones.

  The valid values range from 0 (no slow logging) to 9223372036854775807. The default value is 1000.

  For more information, see this Valkey™ guide.

• Timeout All interfaces

  Time (in seconds) during which connections to inactive clients remain open.

  The valid values range from 0 (connections stay open) to 2147483647.

  For more information, see this Valkey™ guide.