From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v2 docs] pvecm: add qdevice status flag explanation
Date: Tue, 25 Jul 2023 13:00:03 +0200 [thread overview]
Message-ID: <20230725110003.3728126-1-a.lauterer@proxmox.com> (raw)
They are underdocumented and finding information is not that easy.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
changes:
* added reference anchor for easier linking
* use link to manpages.debian.org instead of github
the corosync-doc package does ship HTML documentation, but no man pages,
therefore only the link
pvecm.adoc | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/pvecm.adoc b/pvecm.adoc
index 45271e8..cd8e40d 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -1082,6 +1082,22 @@ Membership information
----
+[[pvecm_qdevice_status_flags]]
+QDevice Status Flags
+^^^^^^^^^^^^^^^^^^^^
+
+The status output of the QDevice, as seen above, will usually contain three
+columns:
+
+* `A` / `NA`: Alive or Not Alive. Indicates if the communication to the external
+ `corosync-qndetd` daemon works.
+* `V` / `NV`: If the QDevice will cast a vote for the node. In a split-brain
+ situation, where the corosync connection between the nodes is down, but they
+ both can still communicate with the external `corosync-qnetd` daemon,
+ only one node will get the vote.
+* `MW` / `NMW`: Master wins (`MV`) or not (`NMW`). Default is `NMW`, see footnote:[`votequorum_qdevice_master_wins` manual page https://manpages.debian.org/bookworm/libvotequorum-dev/votequorum_qdevice_master_wins.3.en.html].
+* `NR`: QDevice is not registered.
+
Frequently Asked Questions
~~~~~~~~~~~~~~~~~~~~~~~~~~
--
2.39.2
next reply other threads:[~2023-07-25 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 11:00 Aaron Lauterer [this message]
2023-07-25 15:21 ` [pve-devel] applied: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230725110003.3728126-1-a.lauterer@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox