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 DDAB81FF136 for ; Mon, 20 Apr 2026 18:43:53 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B7902ACA3; Mon, 20 Apr 2026 18:43:53 +0200 (CEST) From: =?UTF-8?q?Michael=20K=C3=B6ppl?= To: pve-devel@lists.proxmox.com Subject: [PATCH docs v2 3/8] pvecm: add info about warnings regarding token coefficient Date: Mon, 20 Apr 2026 18:43:09 +0200 Message-ID: <20260420164314.370023-4-m.koeppl@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260420164314.370023-1-m.koeppl@proxmox.com> References: <20260420164314.370023-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: 1776703315330 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.101 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: OYBLDGQ5NH4XZYKM26OEHXJOFAZHCYWP X-Message-ID-Hash: OYBLDGQ5NH4XZYKM26OEHXJOFAZHCYWP 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 2d14af11..3d652652 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -1399,6 +1399,11 @@ You can change the token coefficient of an existing cluster by xref:pvecm_edit_corosync_conf[editing corosync.conf]. Corosync will then automatically adopt the new value for the cluster. +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. + Troubleshooting ~~~~~~~~~~~~~~~ -- 2.47.3