From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Friedrich Weber <f.weber@proxmox.com>
Subject: applied: [PATCH pve-cluster 1/2] corosync: create config: allow setting token coefficient
Date: Tue, 3 Mar 2026 18:57:12 +0100 [thread overview]
Message-ID: <177256062155.1651319.11505140861282775816.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260212115928.148999-2-f.weber@proxmox.com>
On Thu, 12 Feb 2026 12:57:55 +0100, Friedrich Weber wrote:
> By default, corosync calculates several timeouts based on the cluster
> size, in particular the token timeout, which is a fixed base value
> plus the number of nodes (minus 2) multipled by a factor called the
> "token coefficient" (with a default of 650ms) [1].
>
> New clusters should be created with a lower token coefficient. Thus,
> allow to pass a custom token coefficient when creating the
> configuration for a new corosync cluster.
>
> [...]
Applied, thanks!
[1/2] corosync: create config: allow setting token coefficient
commit: a7b1c765b9223a81fb2dc4f072d6a6c095583cda
next prev parent reply other threads:[~2026-03-03 17:56 UTC|newest]
Thread overview: 13+ 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-03-03 17:57 ` Thomas Lamprecht [this message]
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-03-03 17:57 ` applied: " Thomas Lamprecht
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
2026-03-03 18:06 ` 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=177256062155.1651319.11505140861282775816.b4-ty@proxmox.com \
--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 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.