CLUSTER INFO
- : State is
ok
if the node is able to receive queries.fail
if there is at least one hash slot which is unbound (no node associated), in error state (node serving it is flagged with FAIL flag), or if the majority of masters can't be reached by this node. cluster_slots_assigned
: Number of slots which are associated to some node (not unbound). This number should be 16384 for the node to work properly, which means that each hash slot should be mapped to a node.cluster_slots_pfail
: Number of hash slots mapping to a node inPFAIL
state. Note that those hash slots still work correctly, as long as the state is not promoted toFAIL
by the failure detection algorithm.PFAIL
only means that we are currently not able to talk with the node, but may be just a transient error.cluster_slots_fail
: Number of hash slots mapping to a node inFAIL
state. If this number is not zero the node is not able to serve queries unlesscluster-require-full-coverage
is set tono
in the configuration.cluster_known_nodes
: The total number of known nodes in the cluster, including nodes inHANDSHAKE
state that may not currently be proper members of the cluster.cluster_current_epoch
: The localCurrent Epoch
variable. This is used in order to create unique increasing version numbers during fail overs.cluster_my_epoch
: TheConfig Epoch
of the node we are talking with. This is the current configuration version assigned to this node.cluster_stats_messages_sent
: Number of messages sent via the cluster node-to-node binary bus.