From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id BC3711FF142 for ; Fri, 05 Jun 2026 17:38:59 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 9CF9F1EAC7; Fri, 5 Jun 2026 17:38:59 +0200 (CEST) From: =?UTF-8?q?Michael=20K=C3=B6ppl?= To: pve-devel@lists.proxmox.com Subject: [PATCH docs v4 2/8] pvecm: add info about warnings regarding token coefficient Date: Fri, 5 Jun 2026 17:38:13 +0200 Message-ID: <20260605153819.310048-3-m.koeppl@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260605153819.310048-1-m.koeppl@proxmox.com> References: <20260605153819.310048-1-m.koeppl@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1780673866009 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.093 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 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: KMRSMNAJVLBXWKUQAPJVXSXMX4OD3NJH X-Message-ID-Hash: KMRSMNAJVLBXWKUQAPJVXSXMX4OD3NJH X-MailFrom: m.koeppl@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: `pvecm status` might warn users of a high sum of token and consensus timeout, recommending lowering the token coefficient. To make users aware that these warnings may occur and to allow users to search for this warning in the docs and man pages, extend the section on lowering the token coefficient. Signed-off-by: Michael Köppl --- pvecm.adoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/pvecm.adoc b/pvecm.adoc index 6469a0c0..d50a2c3a 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -1429,6 +1429,11 @@ so that transient timing variations do not push the cluster past the watchdog threshold. The recommended mechanism for lowering the token and consensus timeouts is lowering the token coefficient as explained below. +Cluster commands may display a warning if the sum of the Corosync token and +consensus timeouts is considered too high (e.g., "Changing the token coefficient +is recommended"). To resolve this warning, it is recommended to lower the token +coefficient. + You can check the current token and consensus timeouts (in milliseconds) with the following command: -- 2.47.3