Skip to content

Commit 6fb9a5e

Browse files
zdover23solmagd
andcommitted
doc/rados: improve leader/peon monitor explanation
Add an explanation of leader-peon conditions that obtain when the cluster is in the "HEALTH_OK" state. Previously, the text discussed these two monitor states only in the context of a health detail entry. This improvement to the documentation was suggested on the [ceph-users] email list by Joel Davidow. This email, an absolute model of user engagement with an upstream project, can be reviewed here: https://lists.ceph.io/hyperkitty/list/[email protected]/message/KF67F5TXFSSTPXV7EKL6JKLA5KZQDLDQ/ I will list Joel Davidow here as the co-author for the sake of more expediently getting this change into the documentation, but though he is listed as the co-author, he is the true author. Co-authored-by: Joel Davidow <[email protected]> Signed-off-by: Zac Dover <[email protected]>
1 parent f66d0b2 commit 6fb9a5e

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

doc/rados/troubleshooting/troubleshooting-mon.rst

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -316,6 +316,12 @@ detail`` returns a message similar to the following::
316316

317317
**What does it mean when a Monitor's state is ``leader`` or ``peon``?**
318318

319+
During normal Ceph operations when the cluster is in the ``HEALTH_OK`` state,
320+
one monitor in the Ceph cluster is in the ``leader`` state and the rest of
321+
the monitors are in the ``peon`` state. The state of a given monitor can be
322+
determined by examining the value of the state key returned by the command
323+
``ceph tell <mon_name> mon_status``.
324+
319325
If ``ceph health detail`` shows that the Monitor is in the ``leader`` state
320326
or in the ``peon`` state, it is likely that clock skew is present. Follow the
321327
instructions in `Clock Skews`_. If you have followed those instructions and

0 commit comments

Comments
 (0)