Administrator’s Command Line Guide

Chapter 4. Monitoring Storage Cluster
Event Severity Description
MDS#<N> (<addr>:<port>) lags
behind for more than 1000
rounds
JRN err Generated by the MDS master server when it detects
that MDS#<N> is stale.
This message may indicate that some MDS server is
very slow and lags behind.
MDS#<N> (<addr>:<port>)
didn’t accept commits for M sec
JRN err Generated by the MDS master server if MDS#<N> did
not accept commits for M seconds. MDS#<N> gets
marked as stale.
This message may indicate that the MDS service on
MDS#<N> is experiencing a problem. The problem
may be critical and should be resolved as soon as pos-
sible.
MDS#<N> (<addr>:<port>) state
is outdated and will do a full
resync
JRN err Generated by the MDS master server when MDS#<N>
will do a full resync. MDS#<N> gets marked as stale.
This message may indicate that some MDS server was
too slow or disconnected for such a long time that it is
not really managing the state of metadata and has to
be resynchronized. The problem may be critical and
should be resolved as soon as possible.
MDS#<N> at <addr>:<port> be-
came master
JRN info Generated every time a new MDS master server is
elected in the cluster.
Frequent changes of MDS masters may indicate poor
network connectivity and may affect the cluster oper-
ation.
The cluster is healthy with N ac-
tive CS
MDS info Generated when the cluster status changes to healthy
or when a new MDS master server is elected.
This message indicates that all chunk servers in the
cluster are active and the number of replicas meets
the set cluster requirements.
56