On 12/02/2026 12:59, Friedrich Weber wrote: > New clusters are created with a lower coefficient. Users with existing > clusters or users who prefer a different token coefficient may want to > change the token coefficient. Hence, add a note how to change the > token coefficient to the admin guide. > > Signed-off-by: Friedrich Weber <[email protected]> > --- > > Notes: > - should this already include more details (in which cases changing > the coefficient may be necessary?) in this first version? > > - currently, changing the token_coefficient in /etc/pve/corosync.conf > without a corosync restart updates token and consensus timeouts, but > knet_ping_timeout and knet_ping_interval are not updated, this is > the reason why the patch suggests a corosync restart. I filed a bug > for this [1] and there is a promising pull request [2] that appears > to fix the issue. So the question is whether we want to backport [2] > (when it's merged), and if yes, whether we want to remove the > restart suggestion from the docs. > > [1] https://github.com/corosync/corosync/issues/813 > [2] https://github.com/corosync/corosync/pull/814
The PR was already merged, I sent a cherry-pick: https://lore.proxmox.com/pve-devel/[email protected]/T/
