You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
master_link_down_since_seconds: now() - last successful ping to master (or last ping received from master)
master_failover_state: TBU
master_link_status: current slave cannot contact with master
slave_read_only: slave only executes read request
slave_priority: a criteria used when promoting slaves to be new master (TBU)
slave_repl_offset: TBU
run_id: unique id of an instance, only null on the first run
slavex:ip=....,port=...,state=...,offset=...,lag=... information of master about slave x, there can be multiple line like this, but the index of a slave should be consistent between calls
Things to consider:
Should we still use text based protocol and read line by line
Should these information be displayed in external info command exposed to user's client, or keep it as an internal command
The text was updated successfully, but these errors were encountered:
Redis' Info commands return a lot of information, but only these are required by Sentinel:
For slave:
Master
Explain:
Things to consider:
The text was updated successfully, but these errors were encountered: