INFO
INFO [section [section ...]]
- Available since:
- 1.0.0
- Time complexity:
- O(1)
- ACL categories:
-
@slow
,@dangerous
,
The INFO
command returns information and statistics about the server in a
format that is simple to parse by computers and easy to read by humans.
The optional parameter can be used to select a specific section of information:
server
: General information about the Redis serverclients
: Client connections sectionmemory
: Memory consumption related informationpersistence
: RDB and AOF related informationstats
: General statisticsreplication
: Master/replica replication informationcpu
: CPU consumption statisticscommandstats
: Redis command statisticslatencystats
: Redis command latency percentile distribution statisticssentinel
: Redis Sentinel section (only applicable to Sentinel instances)cluster
: Redis Cluster sectionmodules
: Modules sectionkeyspace
: Database related statisticserrorstats
: Redis error statistics
It can also take the following values:
all
: Return all sections (excluding module generated ones)default
: Return only the default set of sectionseverything
: Includesall
andmodules
When no parameter is provided, the default
option is assumed.
Notes
Please note depending on the version of Redis some of the fields have been added or removed. A robust client application should therefore parse the result of this command by skipping unknown properties, and gracefully handle missing fields.
Here is the description of fields for Redis >= 2.4.
Here is the meaning of all fields in the server section:
redis_version
: Version of the Redis serverredis_git_sha1
: Git SHA1redis_git_dirty
: Git dirty flagredis_build_id
: The build idredis_mode
: The server's mode ("standalone", "sentinel" or "cluster")os
: Operating system hosting the Redis serverarch_bits
: Architecture (32 or 64 bits)multiplexing_api
: Event loop mechanism used by Redisatomicvar_api
: Atomicvar API used by Redisgcc_version
: Version of the GCC compiler used to compile the Redis serverprocess_id
: PID of the server processprocess_supervised
: Supervised system ("upstart", "systemd", "unknown" or "no")run_id
: Random value identifying the Redis server (to be used by Sentinel and Cluster)tcp_port
: TCP/IP listen portserver_time_usec
: Epoch-based system time with microsecond precisionuptime_in_seconds
: Number of seconds since Redis server startuptime_in_days
: Same value expressed in dayshz
: The server's current frequency settingconfigured_hz
: The server's configured frequency settinglru_clock
: Clock incrementing every minute, for LRU managementexecutable
: The path to the server's executableconfig_file
: The path to the config fileio_threads_active
: Flag indicating if I/O threads are activeshutdown_in_milliseconds
: The maximum time remaining for replicas to catch up the replication before completing the shutdown sequence. This field is only present during shutdown.
Here is the meaning of all fields in the clients section:
connected_clients
: Number of client connections (excluding connections from replicas)cluster_connections
: An approximation of the number of sockets used by the cluster's busmaxclients
: The value of themaxclients
configuration directive. This is the upper limit for the sum ofconnected_clients
,connected_slaves
andcluster_connections
.client_recent_max_input_buffer
: Biggest input buffer among current client connectionsclient_recent_max_output_buffer
: Biggest output buffer among current client connectionsblocked_clients
: Number of clients pending on a blocking call (BLPOP
,BRPOP
,BRPOPLPUSH
,BLMOVE
,BZPOPMIN
,BZPOPMAX
)tracking_clients
: Number of clients being tracked (CLIENT TRACKING
)pubsub_clients
: Number of clients in pubsub mode (SUBSCRIBE
,PSUBSCRIBE
,SSUBSCRIBE
). Added in Redis 7.4watching_clients
: Number of clients in watching mode (WATCH
). Added in Redis 7.4clients_in_timeout_table
: Number of clients in the clients timeout tabletotal_watched_keys
: Number of watched keys. Added in Redis 7.4.total_blocking_keys
: Number of blocking keys. Added in Redis 7.2.total_blocking_keys_on_nokey
: Number of blocking keys that one or more clients that would like to be unblocked when the key is deleted. Added in Redis 7.2.
Here is the meaning of all fields in the memory section:
used_memory
: Total number of bytes allocated by Redis using its allocator (either standard libc, jemalloc, or an alternative allocator such as tcmalloc)used_memory_human
: Human readable representation of previous valueused_memory_rss
: Number of bytes that Redis allocated as seen by the operating system (a.k.a resident set size). This is the number reported by tools such astop(1)
andps(1)
used_memory_rss_human
: Human readable representation of previous valueused_memory_peak
: Peak memory consumed by Redis (in bytes)used_memory_peak_human
: Human readable representation of previous valueused_memory_peak_perc
: The percentage ofused_memory_peak
out ofused_memory
used_memory_overhead
: The sum in bytes of all overheads that the server allocated for managing its internal data structuresused_memory_startup
: Initial amount of memory consumed by Redis at startup in bytesused_memory_dataset
: The size in bytes of the dataset (used_memory_overhead
subtracted fromused_memory
)used_memory_dataset_perc
: The percentage ofused_memory_dataset
out of the net memory usage (used_memory
minusused_memory_startup
)total_system_memory
: The total amount of memory that the Redis host hastotal_system_memory_human
: Human readable representation of previous valueused_memory_lua
: Number of bytes used by the Lua engine for EVAL scripts. Deprecated in Redis 7.0, renamed toused_memory_vm_eval
used_memory_vm_eval
: Number of bytes used by the script VM engines for EVAL framework (not part of used_memory). Added in Redis 7.0used_memory_lua_human
: Human readable representation of previous value. Deprecated in Redis 7.0used_memory_scripts_eval
: Number of bytes overhead by the EVAL scripts (part of used_memory). Added in Redis 7.0number_of_cached_scripts
: The number of EVAL scripts cached by the server. Added in Redis 7.0number_of_functions
: The number of functions. Added in Redis 7.0number_of_libraries
: The number of libraries. Added in Redis 7.0used_memory_vm_functions
: Number of bytes used by the script VM engines for Functions framework (not part of used_memory). Added in Redis 7.0used_memory_vm_total
:used_memory_vm_eval
+used_memory_vm_functions
(not part of used_memory). Added in Redis 7.0used_memory_vm_total_human
: Human readable representation of previous value.used_memory_functions
: Number of bytes overhead by Function scripts (part of used_memory). Added in Redis 7.0used_memory_scripts
:used_memory_scripts_eval
+used_memory_functions
(part of used_memory). Added in Redis 7.0used_memory_scripts_human
: Human readable representation of previous valuemaxmemory
: The value of themaxmemory
configuration directivemaxmemory_human
: Human readable representation of previous valuemaxmemory_policy
: The value of themaxmemory-policy
configuration directivemem_fragmentation_ratio
: Ratio betweenused_memory_rss
andused_memory
. Note that this doesn't only includes fragmentation, but also other process overheads (see theallocator_*
metrics), and also overheads like code, shared libraries, stack, etc.mem_fragmentation_bytes
: Delta betweenused_memory_rss
andused_memory
. Note that when the total fragmentation bytes is low (few megabytes), a high ratio (e.g. 1.5 and above) is not an indication of an issue.allocator_frag_ratio:
: Ratio betweenallocator_active
andallocator_allocated
. This is the true (external) fragmentation metric (notmem_fragmentation_ratio
).allocator_frag_bytes
Delta betweenallocator_active
andallocator_allocated
. See note aboutmem_fragmentation_bytes
.allocator_rss_ratio
: Ratio betweenallocator_resident
andallocator_active
. This usually indicates pages that the allocator can and probably will soon release back to the OS.allocator_rss_bytes
: Delta betweenallocator_resident
andallocator_active
rss_overhead_ratio
: Ratio betweenused_memory_rss
(the process RSS) andallocator_resident
. This includes RSS overheads that are not allocator or heap related.rss_overhead_bytes
: Delta betweenused_memory_rss
(the process RSS) andallocator_resident
allocator_allocated
: Total bytes allocated form the allocator, including internal-fragmentation. Normally the same asused_memory
.allocator_active
: Total bytes in the allocator active pages, this includes external-fragmentation.allocator_resident
: Total bytes resident (RSS) in the allocator, this includes pages that can be released to the OS (byMEMORY PURGE
, or just waiting).allocator_muzzy
: Total bytes of 'muzzy' memory (RSS) in the allocator. Muzzy memory is memory that has been freed, but not yet fully returned to the operating system. It can be reused immediately when needed or reclaimed by the OS when system pressure increases.mem_not_counted_for_evict
: Used memory that's not counted for key eviction. This is basically transient replica and AOF buffers.mem_clients_slaves
: Memory used by replica clients - Starting Redis 7.0, replica buffers share memory with the replication backlog, so this field can show 0 when replicas don't trigger an increase of memory usage.mem_clients_normal
: Memory used by normal clientsmem_cluster_links
: Memory used by links to peers on the cluster bus when cluster mode is enabled.mem_aof_buffer
: Transient memory used for AOF and AOF rewrite buffersmem_replication_backlog
: Memory used by replication backlogmem_total_replication_buffers
: Total memory consumed for replication buffers - Added in Redis 7.0.mem_allocator
: Memory allocator, chosen at compile time.mem_overhead_db_hashtable_rehashing
: Temporary memory overhead of database dictionaries currently being rehashed - Added in 7.4.active_defrag_running
: Whenactivedefrag
is enabled, this indicates whether defragmentation is currently active, and the CPU percentage it intends to utilize.lazyfree_pending_objects
: The number of objects waiting to be freed (as a result of callingUNLINK
, orFLUSHDB
andFLUSHALL
with the ASYNC option)lazyfreed_objects
: The number of objects that have been lazy freed.
Ideally, the used_memory_rss
value should be only slightly higher than
used_memory
.
When rss >> used, a large difference may mean there is (external) memory fragmentation, which can be evaluated by checking
allocator_frag_ratio
, allocator_frag_bytes
.
When used >> rss, it means part of Redis memory has been swapped off by the
operating system: expect some significant latencies.
Because Redis does not have control over how its allocations are mapped to
memory pages, high used_memory_rss
is often the result of a spike in memory
usage.
When Redis frees memory, the memory is given back to the allocator, and the
allocator may or may not give the memory back to the system. There may be
a discrepancy between the used_memory
value and memory consumption as
reported by the operating system. It may be due to the fact memory has been
used and released by Redis, but not given back to the system. The
used_memory_peak
value is generally useful to check this point.
Additional introspective information about the server's memory can be obtained
by referring to the MEMORY STATS
command and the MEMORY DOCTOR
.
Here is the meaning of all fields in the persistence section:
loading
: Flag indicating if the load of a dump file is on-goingasync_loading
: Currently loading replication data-set asynchronously while serving old data. This meansrepl-diskless-load
is enabled and set toswapdb
. Added in Redis 7.0.current_cow_peak
: The peak size in bytes of copy-on-write memory while a child fork is runningcurrent_cow_size
: The size in bytes of copy-on-write memory while a child fork is runningcurrent_cow_size_age
: The age, in seconds, of thecurrent_cow_size
value.current_fork_perc
: The percentage of progress of the current fork process. For AOF and RDB forks it is the percentage ofcurrent_save_keys_processed
out ofcurrent_save_keys_total
.current_save_keys_processed
: Number of keys processed by the current save operationcurrent_save_keys_total
: Number of keys at the beginning of the current save operationrdb_changes_since_last_save
: Number of changes since the last dumprdb_bgsave_in_progress
: Flag indicating a RDB save is on-goingrdb_last_save_time
: Epoch-based timestamp of last successful RDB saverdb_last_bgsave_status
: Status of the last RDB save operationrdb_last_bgsave_time_sec
: Duration of the last RDB save operation in secondsrdb_current_bgsave_time_sec
: Duration of the on-going RDB save operation if anyrdb_last_cow_size
: The size in bytes of copy-on-write memory during the last RDB save operationrdb_last_load_keys_expired
: Number of volatile keys deleted during the last RDB loading. Added in Redis 7.0.rdb_last_load_keys_loaded
: Number of keys loaded during the last RDB loading. Added in Redis 7.0.aof_enabled
: Flag indicating AOF logging is activatedaof_rewrite_in_progress
: Flag indicating a AOF rewrite operation is on-goingaof_rewrite_scheduled
: Flag indicating an AOF rewrite operation will be scheduled once the on-going RDB save is complete.aof_last_rewrite_time_sec
: Duration of the last AOF rewrite operation in secondsaof_current_rewrite_time_sec
: Duration of the on-going AOF rewrite operation if anyaof_last_bgrewrite_status
: Status of the last AOF rewrite operationaof_last_write_status
: Status of the last write operation to the AOFaof_last_cow_size
: The size in bytes of copy-on-write memory during the last AOF rewrite operationmodule_fork_in_progress
: Flag indicating a module fork is on-goingmodule_fork_last_cow_size
: The size in bytes of copy-on-write memory during the last module fork operationaof_rewrites
: Number of AOF rewrites performed since startuprdb_saves
: Number of RDB snapshots performed since startup
rdb_changes_since_last_save
refers to the number of operations that produced
some kind of changes in the dataset since the last time either SAVE
or
BGSAVE
was called.
If AOF is activated, these additional fields will be added:
aof_current_size
: AOF current file sizeaof_base_size
: AOF file size on latest startup or rewriteaof_pending_rewrite
: Flag indicating an AOF rewrite operation will be scheduled once the on-going RDB save is complete.aof_buffer_length
: Size of the AOF bufferaof_rewrite_buffer_length
: Size of the AOF rewrite buffer. Note this field was removed in Redis 7.0aof_pending_bio_fsync
: Number of fsync pending jobs in background I/O queueaof_delayed_fsync
: Delayed fsync counter
If a load operation is on-going, these additional fields will be added:
loading_start_time
: Epoch-based timestamp of the start of the load operationloading_total_bytes
: Total file sizeloading_rdb_used_mem
: The memory usage of the server that had generated the RDB file at the time of the file's creationloading_loaded_bytes
: Number of bytes already loadedloading_loaded_perc
: Same value expressed as a percentageloading_eta_seconds
: ETA in seconds for the load to be complete
Here is the meaning of all fields in the stats section:
total_connections_received
: Total number of connections accepted by the servertotal_commands_processed
: Total number of commands processed by the serverinstantaneous_ops_per_sec
: Number of commands processed per secondtotal_net_input_bytes
: The total number of bytes read from the networktotal_net_output_bytes
: The total number of bytes written to the networktotal_net_repl_input_bytes
: The total number of bytes read from the network for replication purposestotal_net_repl_output_bytes
: The total number of bytes written to the network for replication purposesinstantaneous_input_kbps
: The network's read rate per second in KB/secinstantaneous_output_kbps
: The network's write rate per second in KB/secinstantaneous_input_repl_kbps
: The network's read rate per second in KB/sec for replication purposesinstantaneous_output_repl_kbps
: The network's write rate per second in KB/sec for replication purposesrejected_connections
: Number of connections rejected because ofmaxclients
limitsync_full
: The number of full resyncs with replicassync_partial_ok
: The number of accepted partial resync requestssync_partial_err
: The number of denied partial resync requestsexpired_subkeys
: The number of hash field expiration eventsexpired_keys
: Total number of key expiration eventsexpired_stale_perc
: The percentage of keys probably expiredexpired_time_cap_reached_count
: The count of times that active expiry cycles have stopped earlyexpire_cycle_cpu_milliseconds
: The cumulative amount of time spent on active expiry cyclesevicted_keys
: Number of evicted keys due tomaxmemory
limitevicted_clients
: Number of evicted clients due tomaxmemory-clients
limit. Added in Redis 7.0.evicted_scripts
: Number of evicted EVAL scripts due to LRU policy, seeEVAL
for more details. Added in Redis 7.4.total_eviction_exceeded_time
: Total timeused_memory
was greater thanmaxmemory
since server startup, in millisecondscurrent_eviction_exceeded_time
: The time passed sinceused_memory
last rose abovemaxmemory
, in millisecondskeyspace_hits
: Number of successful lookup of keys in the main dictionarykeyspace_misses
: Number of failed lookup of keys in the main dictionarypubsub_channels
: Global number of pub/sub channels with client subscriptionspubsub_patterns
: Global number of pub/sub pattern with client subscriptionspubsubshard_channels
: Global number of pub/sub shard channels with client subscriptions. Added in Redis 7.0.3latest_fork_usec
: Duration of the latest fork operation in microsecondstotal_forks
: Total number of fork operations since the server startmigrate_cached_sockets
: The number of sockets open forMIGRATE
purposesslave_expires_tracked_keys
: The number of keys tracked for expiry purposes (applicable only to writable replicas)active_defrag_hits
: Number of value reallocations performed by active the defragmentation processactive_defrag_misses
: Number of aborted value reallocations started by the active defragmentation processactive_defrag_key_hits
: Number of keys that were actively defragmentedactive_defrag_key_misses
: Number of keys that were skipped by the active defragmentation processtotal_active_defrag_time
: Total time memory fragmentation was over the limit, in millisecondscurrent_active_defrag_time
: The time passed since memory fragmentation last was over the limit, in millisecondstracking_total_keys
: Number of keys being tracked by the servertracking_total_items
: Number of items, that is the sum of clients number for each key, that are being trackedtracking_total_prefixes
: Number of tracked prefixes in server's prefix table (only applicable for broadcast mode)unexpected_error_replies
: Number of unexpected error replies, that are types of errors from an AOF load or replicationtotal_error_replies
: Total number of issued error replies, that is the sum of rejected commands (errors prior command execution) and failed commands (errors within the command execution)dump_payload_sanitizations
: Total number of dump payload deep integrity validations (seesanitize-dump-payload
config).total_reads_processed
: Total number of read events processedtotal_writes_processed
: Total number of write events processedio_threaded_reads_processed
: Number of read events processed by the main and I/O threadsio_threaded_writes_processed
: Number of write events processed by the main and I/O threadsclient_query_buffer_limit_disconnections
: Total number of disconnections due to client reaching query buffer limitclient_output_buffer_limit_disconnections
: Total number of disconnections due to client reaching output buffer limitreply_buffer_shrinks
: Total number of output buffer shrinksreply_buffer_expands
: Total number of output buffer expandseventloop_cycles
: Total number of eventloop cycleseventloop_duration_sum
: Total time spent in the eventloop in microseconds (including I/O and command processing)eventloop_duration_cmd_sum
: Total time spent on executing commands in microsecondsinstantaneous_eventloop_cycles_per_sec
: Number of eventloop cycles per secondinstantaneous_eventloop_duration_usec
: Average time spent in a single eventloop cycle in microsecondsacl_access_denied_auth
: Number of authentication failuresacl_access_denied_cmd
: Number of commands rejected because of access denied to the commandacl_access_denied_key
: Number of commands rejected because of access denied to a keyacl_access_denied_channel
: Number of commands rejected because of access denied to a channel
Here is the meaning of all fields in the replication section:
role
: Value is "master" if the instance is replica of no one, or "slave" if the instance is a replica of some master instance. Note that a replica can be master of another replica (chained replication).master_failover_state
: The state of an ongoing failover, if any.master_replid
: The replication ID of the Redis server.master_replid2
: The secondary replication ID, used for PSYNC after a failover.master_repl_offset
: The server's current replication offsetsecond_repl_offset
: The offset up to which replication IDs are acceptedrepl_backlog_active
: Flag indicating replication backlog is activerepl_backlog_size
: Total size in bytes of the replication backlog bufferrepl_backlog_first_byte_offset
: The master offset of the replication backlog bufferrepl_backlog_histlen
: Size in bytes of the data in the replication backlog buffer
If the instance is a replica, these additional fields are provided:
master_host
: Host or IP address of the mastermaster_port
: Master listening TCP portmaster_link_status
: Status of the link (up/down)master_last_io_seconds_ago
: Number of seconds since the last interaction with mastermaster_sync_in_progress
: Indicate the master is syncing to the replicaslave_read_repl_offset
: The read replication offset of the replica instance.slave_repl_offset
: The replication offset of the replica instanceslave_priority
: The priority of the instance as a candidate for failoverslave_read_only
: Flag indicating if the replica is read-onlyreplica_announced
: Flag indicating if the replica is announced by Sentinel.
If a SYNC operation is on-going, these additional fields are provided:
master_sync_total_bytes
: Total number of bytes that need to be transferred. this may be 0 when the size is unknown (for example, when therepl-diskless-sync
configuration directive is used)master_sync_read_bytes
: Number of bytes already transferredmaster_sync_left_bytes
: Number of bytes left before syncing is complete (may be negative whenmaster_sync_total_bytes
is 0)master_sync_perc
: The percentagemaster_sync_read_bytes
frommaster_sync_total_bytes
, or an approximation that usesloading_rdb_used_mem
whenmaster_sync_total_bytes
is 0master_sync_last_io_seconds_ago
: Number of seconds since last transfer I/O during a SYNC operation
If the link between master and replica is down, an additional field is provided:
master_link_down_since_seconds
: Number of seconds since the link is down
The following field is always provided:
connected_slaves
: Number of connected replicas
If the server is configured with the min-slaves-to-write
(or starting with Redis 5 with the min-replicas-to-write
) directive, an additional field is provided:
min_slaves_good_slaves
: Number of replicas currently considered good
For each replica, the following line is added:
slaveXXX
: id, IP address, port, state, offset, lag
Here is the meaning of all fields in the cpu section:
used_cpu_sys
: System CPU consumed by the Redis server, which is the sum of system CPU consumed by all threads of the server process (main thread and background threads)used_cpu_user
: User CPU consumed by the Redis server, which is the sum of user CPU consumed by all threads of the server process (main thread and background threads)used_cpu_sys_children
: System CPU consumed by the background processesused_cpu_user_children
: User CPU consumed by the background processesused_cpu_sys_main_thread
: System CPU consumed by the Redis server main threadused_cpu_user_main_thread
: User CPU consumed by the Redis server main thread
The commandstats section provides statistics based on the command type, including the number of calls that reached command execution (not rejected), the total CPU time consumed by these commands, the average CPU consumed per command execution, the number of rejected calls (errors prior command execution), and the number of failed calls (errors within the command execution).
For each command type, the following line is added:
cmdstat_XXX
:calls=XXX,usec=XXX,usec_per_call=XXX,rejected_calls=XXX,failed_calls=XXX
The latencystats section provides latency percentile distribution statistics based on the command type.
By default, the exported latency percentiles are the p50, p99, and p999.
If you need to change the exported percentiles, use CONFIG SET latency-tracking-info-percentiles "50.0 99.0 99.9"
.
This section requires the extended latency monitoring feature to be enabled (by default it's enabled).
If you need to enable it, use CONFIG SET latency-tracking yes
.
For each command type, the following line is added:
latency_percentiles_usec_XXX: p<percentile 1>=<percentile 1 value>,p<percentile 2>=<percentile 2 value>,...
The errorstats section enables keeping track of the different errors that occurred within Redis,
based upon the reply error prefix ( The first word after the "-", up to the first space. Example: ERR
).
For each error type, the following line is added:
errorstat_XXX
:count=XXX
If the server detects that this section was flooded with an excessive number of errors, it will be disabled, show a single ERRORSTATS_DISABLED
error, and print the errors to the server log.
This can be reset by CONFIG RESETSTAT
.
The sentinel section is only available in Redis Sentinel instances. It consists of the following fields:
sentinel_masters
: Number of Redis masters monitored by this Sentinel instancesentinel_tilt
: A value of 1 means this sentinel is in TILT modesentinel_tilt_since_seconds
: Duration in seconds of current TILT, or -1 if not TILTed. Added in Redis 7.0.0sentinel_running_scripts
: The number of scripts this Sentinel is currently executingsentinel_scripts_queue_length
: The length of the queue of user scripts that are pending executionsentinel_simulate_failure_flags
: Flags for theSENTINEL SIMULATE-FAILURE
command
The cluster section currently only contains a unique field:
cluster_enabled
: Indicate Redis cluster is enabled
The modules section contains additional information about loaded modules if the modules provide it. The field part of properties lines in this section is always prefixed with the module's name.
The keyspace section provides statistics on the main dictionary of each database. The statistics are the number of keys, and the number of keys with an expiration.
For each database, the following line is added:
dbXXX
:keys=XXX,expires=XXX,avg_ttl=XXX,subexpiry=XXX
The debug section contains experimental metrics, which might change or get removed in future versions.
It won't be included when INFO
or INFO ALL
are called, and it is returned only when INFO DEBUG
is used.
eventloop_duration_aof_sum
: Total time spent on flushing AOF in eventloop in microseconds.eventloop_duration_cron_sum
: Total time consumption of cron in microseconds (including serverCron and beforeSleep, but excluding IO and AOF flushing).eventloop_duration_max
: The maximal time spent in a single eventloop cycle in microseconds.eventloop_cmd_per_cycle_max
: The maximal number of commands processed in a single eventloop cycle.allocator_allocated_lua
: Total bytes allocated from the allocator specifically for Lua, including internal-fragmentation.allocator_active_lua
: Total bytes in the allocator active pages specifically for Lua, including external-fragmentation.allocator_resident_lua
: Total bytes resident (RSS) in the allocator specifically for Lua. This includes pages that can be released to the OS (byMEMORY PURGE
, or just waiting).allocator_frag_bytes_lua
: Delta betweenallocator_active_lua
andallocator_allocated_lua
.
A note about the word slave used in this man page: Starting with Redis 5, if not for backward compatibility, the Redis project no longer uses the word slave. Unfortunately in this command the word slave is part of the protocol, so we'll be able to remove such occurrences only when this API will be naturally deprecated.
Modules generated sections: Starting with Redis 6, modules can inject their information into the INFO
command. These are excluded by default even when the all
argument is provided (it will include a list of loaded modules but not their generated info fields). To get these you must use either the modules
argument or everything
.
RESP2/RESP3 Reply
Bulk string reply: a map of info fields, one field per line in the form of <field>:<value>
where the value can be a comma separated map like <key>=<val>
. Also contains section header lines starting with #
and blank lines.
Lines can contain a section name (starting with a #
character) or a property. All the properties are in the form of field:value
terminated by \r\n
.
History
- Starting with Redis version 7.0.0: Added support for taking multiple section arguments.