public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Manuel Federanko <m.federanko@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH docs] qdevice: correct qdevice partition tie breaking section.
Date: Fri, 20 Feb 2026 14:27:28 +0100	[thread overview]
Message-ID: <s8ozf53a6kf.fsf@proxmox.com> (raw)
In-Reply-To: <20260220125709.59612-1-m.federanko@proxmox.com> (Manuel Federanko's message of "Fri, 20 Feb 2026 13:57:09 +0100")

Manuel Federanko <m.federanko@proxmox.com> writes:

> The partition that gets a vote is not randomly chosen, but depends on
> the configuration of the qdevice in corosync.conf.
>
> A partner asked about predictable behavior for vote casting by the
> QDevice. The documentation of corosync and ours didn't align.
>
> Setting tie_breaker influences how a partition is chosen for votes,
> which was tested with a 2-node test-cluster.
>
> Signed-off-by: Manuel Federanko <m.federanko@proxmox.com>
> ---
>  pvecm.adoc | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/pvecm.adoc b/pvecm.adoc
> index 0ed1bd2..899a4de 100644
> --- a/pvecm.adoc
> +++ b/pvecm.adoc
> @@ -1266,8 +1266,10 @@ Tie Breaking
>  ^^^^^^^^^^^^
>  
>  In case of a tie, where two same-sized cluster partitions cannot see each other
> -but can see the QDevice, the QDevice chooses one of those partitions randomly
> -and provides a vote to it.
> +but can see the QDevice, the QDevice chooses the partition which has
> +the lowest node id and provides a vote to it. This behavior can be tuned with
> +the configuration option `tie_breaker` (see `man corosync-qdevice` for more
> +information) and requires a restart of `corosync-qdevice.service` on all nodes.
>  
>  Possible Negative Implications
>  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I would personally only mention the man page so to avoid running out of
sync, but this looks good to me as-is.

Reviewed-by: Maximiliano Sandoval <m.sandoval@proxmox.com>

-- 
Maximiliano




      reply	other threads:[~2026-02-20 13:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-20 12:57 Manuel Federanko
2026-02-20 13:27 ` Maximiliano Sandoval [this message]

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=s8ozf53a6kf.fsf@proxmox.com \
    --to=m.sandoval@proxmox.com \
    --cc=m.federanko@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal