INFO

Reports server or replication status information.

Server & administration · Example verified

Syntax covered here

INFO server | INFO replication

The cases identify the pinned Lavik version and standalone master role; these status fields do not demonstrate a working replication topology.

Tested example & replies

Requests below run in order against an empty database. Each connection authenticates with the fixture password first. Quoted values are strings; null is a nil reply; arrays preserve RESP order.

# connection: default
> INFO server
"# Server\r\nlavik_version:0.2.0\r\nredis_mode:standalone\r\nprocess_id:11\r\nrun_id:9fc9da211a15c5762bd4689e9acbe385f42848f7\r\ntcp_port:6379\r\nworker_threads:2\r\nuptime_in_seconds:11\r\n\r\n"
# connection: default
> INFO replication
"# Replication\r\nrole:master\r\nlavik_replication_state:master\r\nlavik_replication_failed_stopped:0\r\nlavik_replication_role_epoch:0\r\nlavik_replication_group_id:a1df20f46033c40fe05c2bb435090dfb22acfafa\r\nlavik_replication_boot_id:84679f61a9d86e0630a28e6e005a146801f2200a\r\nlavik_replica_incarnation:f0e504b3606997d1d3dd76705f5a8595448bab9d\r\nlavik_function_catalog_generation:9\r\nlavik_function_catalog_crc64:0\r\nmaster_replid:0c730d4d20278d20befa25332f83ac3478991301\r\nmaster_replid2:0000000000000000000000000000000000000000\r\nredis_export_active:0\r\nredis_export_session_id:0\r\nredis_export_group_id:\r\nredis_export_node_id:\r\nredis_export_boot_id:\r\nredis_export_term:0\r\nredis_export_generation:0\r\nredis_export_disk_capacity:0\r\nredis_export_history_id:\r\nredis_export_phase:inactive\r\nredis_export_offset:1\r\nredis_export_source_next_lsns:\r\nredis_export_sent_next_lsns:\r\nmaster_repl_offset:0\r\nsecond_repl_offset:-1\r\nlavik_full_sync_sessions:0\r\nconnected_slaves:0\r\n\r\n"