INFO
Reports server or replication status information.
Server & administration · Example verified
Syntax covered here
INFO server | INFO replicationThe 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.1.0-beta.1\r\nredis_mode:standalone\r\nprocess_id:11\r\nrun_id:dfc20827365c128fc55f7ff707fa859daa817842\r\ntcp_port:6379\r\nworker_threads:2\r\nuptime_in_seconds:1\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:8241f8a61049cf00b641d37aae430794bb9b19c2\r\nlavik_replication_boot_id:2db04fd270c3b2fa26801c0328d8aa96f4fb3bfd\r\nlavik_replica_incarnation:ebbb0a543c6ba263c700d9b41cf4889f9a253907\r\nlavik_function_catalog_generation:9\r\nlavik_function_catalog_crc64:0\r\nmaster_replid:1c9128313a1a864c51191430628b989bf74b89a6\r\nmaster_replid2:0000000000000000000000000000000000000000\r\nmaster_repl_offset:0\r\nsecond_repl_offset:-1\r\nconnected_slaves:0\r\n\r\n"Test environment & reproducible evidence
Verified: 2026-09-21T11:06:06Z · Docker / Linux aarch64 · lavik 0.1.0-beta.1
Storage & connection: io_uring · temporary file, 2 workers, standalone, plaintext TCP, password authentication. This test does not measure NVMe performance.
Pinned source: 3955b98d43b312324aa8d52775df52cfb111c0d0
Binary SHA-256: 8306b37ddf05023f85166a6aa2192b7084757e8defd342b602e6470244aca887
Image: sha256:af0cfb11b78f184cb6cc49a774a49dc97a8e43a0bd3f4d63d83c8c9ef3282d6e
Lavik command registry · Valkey counterpart (support may differ)