This page describes the available options for Redis configurations that can be changed on Cloud Memorystore instances and the default values chosen for the ones that cannot.
When your Redis instance memory is full, and a new write comes in, Redis evicts
keys to make room for the write based on your instance's maxmemory policy. The
default maxmemory policy for Cloud Memorystore is
can also use one of the following maxmemory policies:
noeviction: Returns an error when the Redis instance reaches maxmemory. Does not overwrite or evict any data.
allkeys-lfu: Available in Redis version 4.0, or later. Evicts the least frequently used (LFU) keys from the entire keyset.
allkeys-lru: Evicts the least recently used (LRU) keys from the entire keyset.
volatile-lfu: Available in Redis version 4.0, or later. Evicts the least-frequently-used keys that are set with TTL (time to live) expirations.
volatile-lru: Evicts the least recently used (LRU) keys that are set with TTL expirations.
allkeys-random: Evicts random keys from the entire keyspace.
volatile-random: Evicts random keys from among those set with TTL expirations.
volatile-ttl: Evicts the keys with the shortest TTL from among those set with TTL expirations.
Modifiable configuration parameters
You can modify the following parameters when creating or updating a Cloud Memorystore instance. You do not need to restart your instance after modifying any of the following parameters. For more information about how to change these configurations, see Configuring Redis Instances.
|activedefrag||Redis version 4.0, or later. Works to free up instance memory tied up by standard OSS Redis memory fragmentation behavior.|
|lfu-decay-time||Redis version 4.0, or later. The time, in minutes, before the LFU frequency counter for a given key will be divided by two (or, if the counter is < 10, decremented by 1). See the REDIS.CONF file for additional information.||Positive integers of the 'long' data type
|lfu-log-factor||Redis version 4.0, or later. Determines how the frequency counter represents key hits. Before you modify the default configuration, read about how the
||Positive integers of the 'long' data type
|maxmemory-gb|| Designates an adjustable limit at which your eviction policy takes effect.
For example, if you have a 10 GB instance and you set
|Number of GB expressed as a whole number or decimal.
|maxmemory-policy||Specifies the behavior Redis follows when the instance data reaches the
|notify-keyspace-events||Allows clients to subscribe to notifications on certain keyspace events. See the Redis Keyspace Notifications page on the Redis site for more information.||
Keyspace events, published with __keyspace@
Keyevent events, published with __keyevent@
Generic commands (non-type specific) like DEL, EXPIRE, or RENAME
Sorted set commands
Expired events (events generated every time a key expires)
Evicted events (events generated when a key is evicted for maxmemory)
Alias for g$lshzxe, so that the "AKE" string means all the events.
Unmodifiable configuration parameters
The following table lists the Redis configuration parameters that you cannot modify in Cloud Memorystore and their default values. See the Redis configuration documentation for detailed information about these configuration parameters.
Blocked Redis commands