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
