all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 2/2] pvecm: add qdevice status flag explanation
Date: Mon, 24 Jul 2023 14:54:31 +0200	[thread overview]
Message-ID: <20230724125431.2492297-2-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20230724125431.2492297-1-a.lauterer@proxmox.com>

They are underdocumented and finding information is not that easy.

Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---

Found some info in the suse documentation [0] and the sourcecode [1].
We do not ship man 3 pages, therefore I used a direct link to the github
repo as that seems to be the only place that talks abit about the MW /
NMW flag.

[0] https://documentation.suse.com/sle-ha/15-SP1/html/SLE-HA-all/cha-ha-qdevice.html
[1] https://github.com/corosync/corosync/blob/v3.1.7/tools/corosync-quorumtool.c#L524-L536


 pvecm.adoc | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/pvecm.adoc b/pvecm.adoc
index 45271e8..e286bdd 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -1082,6 +1082,21 @@ Membership information
 
 ----
 
+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://github.com/corosync/corosync/blob/main/man/votequorum_qdevice_master_wins.3.in].
+* `NR`: QDevice is not registered.
+
 
 Frequently Asked Questions
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
-- 
2.39.2





  reply	other threads:[~2023-07-24 12:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24 12:54 [pve-devel] [PATCH docs 1/2] pvecm: fix pvecm status indentation Aaron Lauterer
2023-07-24 12:54 ` Aaron Lauterer [this message]
2023-07-25  9:17   ` [pve-devel] [PATCH docs 2/2] pvecm: add qdevice status flag explanation Thomas Lamprecht
2023-07-25  9:35     ` Aaron Lauterer
2023-07-25  9:56 ` [pve-devel] applied: [PATCH docs 1/2] pvecm: fix pvecm status indentation 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=20230724125431.2492297-2-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal