From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Friedrich Weber <f.weber@proxmox.com>
Subject: applied: [PATCH pve-cluster 2/2] api: cluster config: create new clusters with lower token coefficient
Date: Tue, 3 Mar 2026 18:57:13 +0100 [thread overview]
Message-ID: <177256062155.1651319.11049715542414622494.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260212115928.148999-3-f.weber@proxmox.com>
On Thu, 12 Feb 2026 12:57:56 +0100, Friedrich Weber wrote:
> corosync makes use of several timeouts, in particular the token and
> consensus timeouts. The sum of these two timeouts yields the minimum
> time a cluster needs to reestablish a membership after a token loss
> due to a complete node failure.
>
> By default, corosync sets the timeouts based on the cluster size [1]:
>
> [...]
Applied, thanks!
[2/2] api: cluster config: create new clusters with lower 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 " Friedrich Weber
2026-02-12 11:57 ` [PATCH pve-cluster 1/2] corosync: create config: allow setting " Friedrich Weber
2026-03-03 17:57 ` applied: " Thomas Lamprecht
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 ` Thomas Lamprecht [this message]
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.11049715542414622494.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.