From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Friedrich Weber <f.weber@proxmox.com>
Subject: applied: [PATCH docs v2] pvecm: elaborate when and how to change the token coefficient
Date: Tue, 19 May 2026 20:10:17 +0200 [thread overview]
Message-ID: <177921421605.2365214.4866682372931385491.b4-ty@b4> (raw)
In-Reply-To: <20260519173900.383644-1-f.weber@proxmox.com>
On Tue, 19 May 2026 19:38:58 +0200, Friedrich Weber wrote:
> Since pve-cluster 9.1.0, more specifically commit a7b1c76 ("corosync
> config: allow to override token coefficient and lower default"), new
> corosync clusters are created with a token_coefficient of 125ms (the
> default being 650ms), primarily to avoid issues with larger clusters
> in combination with HA.
>
> Already existing clusters may need manual adjustment of the
> token_coefficient. Hence, expand the "Changing the Token Coefficient"
> section and provide instructions when and how to change the token
> coefficient.
>
> [...]
Applied, thanks!
[1/1] pvecm: elaborate when and how to change the token coefficient
commit: a5a6434316d615c9d7bfce8c25f10825915afb11
prev parent reply other threads:[~2026-05-19 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 17:38 [PATCH docs v2] pvecm: elaborate when and how to change the token coefficient Friedrich Weber
2026-05-19 18:10 ` Thomas Lamprecht [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=177921421605.2365214.4866682372931385491.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=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