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
