Skip to main content
The Redis Configuration page allows you to view and modify runtime configuration parameters. Changes take effect immediately but require CONFIG REWRITE to persist across server restarts.

​
Key Concepts

Runtime Config

Parameters that can be changed without restarting Redis. Most settings support runtime modification.

Persistent Config

Configuration stored in redis.conf. Use CONFIG REWRITE to save runtime changes permanently.

Read-Only Parameters

Some parameters cannot be changed at runtime and require a server restart.

Categories

Configurations are grouped by function: Memory, Persistence, Networking, Security, and more.

​
Required Permissions

ActionPermission
View configurationiam:project:infrastructure:redis:read
Modify configurationiam:project:infrastructure:redis:write

​
Configuration Categories

CategoryDescriptionExamples
MemoryMemory limits and managementmaxmemory, hash-max-ziplist-entries
PersistenceAOF and RDB settingsappendonly, save, rdb-compression
NetworkingConnection and timeout settingsbind, port, tcp-keepalive, timeout
SecurityAuthentication and access controlrequirepass, protected-mode
ReplicationMaster-replica configurationreplicaof, min-replicas-to-write
ClientsClient connection limitsmaxclients, client-output-buffer-limit
LoggingSlow log and latency trackingslowlog-log-slower-than, slowlog-max-len

​
How to View Configuration

1

Select Connection

Choose a Redis connection from the dropdown.
2

Browse Parameters

All configuration parameters are displayed in a searchable table.
3

Filter by Category

Use the category filter to show only parameters in a specific group.
4

Search Parameters

Type in the search box to find specific parameters by name or value.

​
How to Modify Configuration

1

Find the Parameter

Search or browse to locate the parameter you want to change.
2

Click Edit

Click the edit button on the parameter row.
3

Enter New Value

Type the new value in the input field.
4

Save

Click the checkmark to apply the change. Click X to cancel.
Configuration changes take effect immediately but are not persisted to redis.conf. Run CONFIG REWRITE in Redis CLI to save changes permanently.

​
Common Settings

​
Memory Configuration

ParameterDescriptionDefault
maxmemoryMaximum memory limit (0 = unlimited)0
maxmemory-policyEviction policy when limit is reachednoeviction
hash-max-ziplist-entriesMax entries for ziplist encoding512
hash-max-ziplist-valueMax value size for ziplist encoding64

​
Eviction Policies

PolicyDescription
noevictionReturn error when memory limit reached
allkeys-lruEvict least recently used keys
allkeys-lfuEvict least frequently used keys
volatile-lruEvict LRU keys with TTL set
volatile-lfuEvict LFU keys with TTL set
allkeys-randomEvict random keys
volatile-randomEvict random keys with TTL set
volatile-ttlEvict keys with shortest TTL

​
Client Configuration

ParameterDescriptionDefault
maxclientsMaximum concurrent connections10000
timeoutClient idle timeout in seconds (0 = disabled)0
tcp-keepaliveTCP keepalive interval in seconds300

​
Slow Log Configuration

ParameterDescriptionDefault
slowlog-log-slower-thanLog commands slower than N microseconds10000
slowlog-max-lenMaximum slow log entries to keep128
Set slowlog-log-slower-than to 0 to log all commands, or -1 to disable slow logging.

​
Persistence Configuration

ParameterDescriptionDefault
appendonlyEnable AOF persistenceno
appendfsyncAOF fsync policy (always, everysec, no)everysec
saveRDB snapshot triggersVarious

​
How to Persist Configuration Changes

Runtime changes are lost on restart unless persisted.
1

Make Changes

Modify configuration parameters through the UI.
2

Open Redis CLI

Navigate to Redis > CLI or use an external Redis CLI.
3

Run CONFIG REWRITE

Execute CONFIG REWRITE to save current configuration to redis.conf.
# In Redis CLI
CONFIG REWRITE
CONFIG REWRITE requires write access to the redis.conf file. It may fail if Redis was started without a config file or lacks file permissions.

​
Troubleshooting

  • You need write permission
  • Some parameters are read-only and require restart
  • The server may be in read-only mode
  • Check if the parameter name is correct
  • Run CONFIG REWRITE to save changes to redis.conf
  • Verify Redis has write access to the config file
  • Check if Redis was started with a config file
  • Redis may not have write permission to config file
  • Redis may have been started without a config file
  • File system may be read-only
  • Check Redis logs for specific error
  • Check Redis version (some parameters are version-specific)
  • Verify parameter name spelling
  • Some parameters are aliases (e.g., slaveof vs replicaof)
  • Check the expected value format
  • Memory values use K, M, G suffixes (e.g., 100mb)
  • Boolean values use yes/no, not true/false
  • Time values may be in seconds or milliseconds
  • Revert the change using the same edit process
  • Common causes: maxmemory too low, aggressive eviction
  • Check Redis INFO for memory and eviction stats
  • Monitor slow log for performance impact

​
FAQ

Runtime (dynamic) configuration can be changed while Redis is running using CONFIG SET. Static configuration requires editing redis.conf and restarting the server. Most parameters support runtime modification.
Run CONFIG GET dir to get the working directory and CONFIG GET dbfilename for the database file. The redis.conf is typically in the same directory or /etc/redis/.
Depending on maxmemory-policy: noeviction returns errors on writes, eviction policies delete keys to free memory. Monitor evicted_keys in INFO stats to detect excessive eviction.
RDB provides point-in-time snapshots, good for backups but potential data loss. AOF logs every write, better durability but larger files. Many production systems use both.
Default is 10000 microseconds (10ms). For production, 1000-10000 is typical. Set lower for debugging, higher if slow log fills too quickly. Use 0 to log everything.
Use CONFIG SET with the default value. Alternatively, restart Redis without the parameter in redis.conf to restore defaults.
Most changes are immediate and safe. Memory-related changes may trigger eviction. Persistence changes may affect disk I/O. Test in non-production first.
Empty values typically mean the parameter uses a default or is disabled. For example, an empty bind means Redis listens on all interfaces.

​
Best Practices

​
Before Making Changes

  • Document current values before modifying
  • Understand the impact of each parameter
  • Test changes in non-production environments first
  • Have a rollback plan ready

​
Memory Configuration

  • Set maxmemory to leave headroom for overhead
  • Choose appropriate eviction policy for your use case
  • Monitor memory usage after changes
  • Consider fragmentation when setting limits

​
Performance Tuning

  • Start with defaults, adjust based on monitoring
  • Use slow log to identify bottlenecks
  • Tune tcp-keepalive based on network environment
  • Adjust maxclients based on expected load

​
Persistence Settings

  • Balance durability vs performance with appendfsync
  • Configure save points based on data change rate
  • Monitor disk I/O after persistence changes
  • Test backup and recovery procedures

​
Security Settings

  • Enable protected-mode in production
  • Set strong requirepass for authentication
  • Consider ACL for fine-grained access (Redis 6+)
  • Limit bind addresses to required interfaces