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 469C81FF141 for ; Tue, 19 May 2026 20:10:30 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BC5E2F5A7; Tue, 19 May 2026 20:10:27 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Friedrich Weber Subject: applied: [PATCH docs v2] pvecm: elaborate when and how to change the token coefficient Date: Tue, 19 May 2026 20:10:17 +0200 Message-ID: <177921421605.2365214.4866682372931385491.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260519173900.383644-1-f.weber@proxmox.com> References: <20260519173900.383644-1-f.weber@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: 1779214209348 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.004 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: GEJFNTA4WAVTQAU3XSZ6IZFDPQG6SKBD X-Message-ID-Hash: GEJFNTA4WAVTQAU3XSZ6IZFDPQG6SKBD X-MailFrom: t.lamprecht@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: On Tue, 19 May 2026 19:38:58 +0200, Friedrich Weber wrote: > Since pve-cluster 9.1.0, more specifically commit a7b1c76 ("corosync > config: allow to override token coefficient and lower default"), new > corosync clusters are created with a token_coefficient of 125ms (the > default being 650ms), primarily to avoid issues with larger clusters > in combination with HA. > > Already existing clusters may need manual adjustment of the > token_coefficient. Hence, expand the "Changing the Token Coefficient" > section and provide instructions when and how to change the token > coefficient. > > [...] Applied, thanks! [1/1] pvecm: elaborate when and how to change the token coefficient commit: a5a6434316d615c9d7bfce8c25f10825915afb11