public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Friedrich Weber <f.weber@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [PATCH pve-docs 1/1] pvecm: config: document how to change the token coefficient
Date: Fri, 13 Feb 2026 11:12:58 +0100	[thread overview]
Message-ID: <3d5c2533-3270-4c8d-b4d2-a774cd2fc46c@proxmox.com> (raw)
In-Reply-To: <20260212115928.148999-4-f.weber@proxmox.com>

On 12/02/2026 12:59, Friedrich Weber wrote:
> New clusters are created with a lower coefficient. Users with existing
> clusters or users who prefer a different token coefficient may want to
> change the token coefficient. Hence, add a note how to change the
> token coefficient to the admin guide.
> 
> Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
> ---
> 
> Notes:
>     - should this already include more details (in which cases changing
>       the coefficient may be necessary?) in this first version?
>     
>     - currently, changing the token_coefficient in /etc/pve/corosync.conf
>       without a corosync restart updates token and consensus timeouts, but
>       knet_ping_timeout and knet_ping_interval are not updated, this is
>       the reason why the patch suggests a corosync restart. I filed a bug
>       for this [1] and there is a promising pull request [2] that appears
>       to fix the issue. So the question is whether we want to backport [2]
>       (when it's merged), and if yes, whether we want to remove the
>       restart suggestion from the docs.
>     
>     [1] https://github.com/corosync/corosync/issues/813
>     [2] https://github.com/corosync/corosync/pull/814

The PR was already merged, I sent a cherry-pick:
https://lore.proxmox.com/pve-devel/20260213101121.107073-1-f.weber@proxmox.com/T/




      reply	other threads:[~2026-02-13 10:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-12 11:57 [PATCH cluster/docs 0/3] create new corosync clusters with lower " Friedrich Weber
2026-02-12 11:57 ` [PATCH pve-cluster 1/2] corosync: create config: allow setting " Friedrich Weber
2026-02-12 11:57 ` [PATCH pve-cluster 2/2] api: cluster config: create new clusters with lower " Friedrich Weber
2026-02-16 16:00   ` Maximiliano Sandoval
2026-02-16 19:36     ` Thomas Lamprecht
2026-02-17 12:44       ` Maximiliano Sandoval
2026-02-17 12:50         ` Friedrich Weber
2026-02-16 16:09   ` Maximiliano Sandoval
2026-02-12 11:57 ` [PATCH pve-docs 1/1] pvecm: config: document how to change the " Friedrich Weber
2026-02-13 10:12   ` Friedrich Weber [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=3d5c2533-3270-4c8d-b4d2-a774cd2fc46c@proxmox.com \
    --to=f.weber@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