From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 739141FF13F for ; Thu, 12 Feb 2026 12:59:12 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 30334DDBA; Thu, 12 Feb 2026 12:59:46 +0100 (CET) From: Friedrich Weber To: pve-devel@lists.proxmox.com Subject: [PATCH pve-docs 1/1] pvecm: config: document how to change the token coefficient Date: Thu, 12 Feb 2026 12:57:57 +0100 Message-ID: <20260212115928.148999-4-f.weber@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260212115928.148999-1-f.weber@proxmox.com> References: <20260212115928.148999-1-f.weber@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1770897576457 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.012 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: JRAPNVDOMMPGCRHQFN6BGSTGWUW4W7LN X-Message-ID-Hash: JRAPNVDOMMPGCRHQFN6BGSTGWUW4W7LN X-MailFrom: f.weber@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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 --- 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 pvecm.adoc | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/pvecm.adoc b/pvecm.adoc index 0ed1bd2..9513a6c 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -1371,6 +1371,23 @@ systemctl restart corosync On errors, check the troubleshooting section below. +Changing the token cofficient +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The token coefficient can be configured in the `totem` section in +`/etc/pve/corosync.conf`. corosync uses the token coefficient to calculate +several timeouts in relation to the cluster size.footnote:[ +`token_coefficient` in the corosync manual page +https://manpages.debian.org/stable/corosync/corosync.conf.5.en.html#token_coefficient] + +If the token coefficient is not explicitly set, it defaults to 650 milliseconds. +New clusters are created with a lower token coefficient of 125ms that is +explicitly set in `/etc/pve/corosync.conf`. + +You can change the token coefficient of an existing cluster by +xref:pvecm_edit_corosync_conf[editing corosync.conf]. For the change to fully +take effect, you need to restart corosync on all nodes. + Troubleshooting ~~~~~~~~~~~~~~~ -- 2.47.3