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 A48921FF13F for ; Thu, 12 Feb 2026 12:59:27 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8008FDE44; Thu, 12 Feb 2026 13:00:13 +0100 (CET) From: Friedrich Weber To: pve-devel@lists.proxmox.com Subject: [PATCH cluster/docs 0/3] create new corosync clusters with lower token coefficient Date: Thu, 12 Feb 2026 12:57:54 +0100 Message-ID: <20260212115928.148999-1-f.weber@proxmox.com> X-Mailer: git-send-email 2.47.3 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: 1770897576261 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: 7ZPEV466435QX2SK3CUBB5GY46E4NO3I X-Message-ID-Hash: 7ZPEV466435QX2SK3CUBB5GY46E4NO3I 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: corosync calculates certain timeouts based on the cluster size. As a result, after a node failure in a cluster with default corosync settings and more than ~30 nodes, the time until corosync reestablishes a membership can get close to or exceed 50-60s. In an HA cluster, this can be too long because the watchdog may start fencing nodes after ~60 seconds without a membership. To avoid this, create new corosync clusters with smaller timeouts. See patch #2 for more details. In a future patch series, we may also want to detect problematic settings at certain points and notify the user accordingly (e.g. when adding a new node or in `pvecm status`). This will also benefit users with existing clusters with more than ~30 nodes. pve-cluster: Friedrich Weber (2): corosync: create config: allow setting token coefficient api: cluster config: create new clusters with lower token coefficient src/PVE/API2/ClusterConfig.pm | 9 +++++++++ src/PVE/Corosync.pm | 3 +++ 2 files changed, 12 insertions(+) pve-docs: Friedrich Weber (1): pvecm: config: document how to change the token coefficient pvecm.adoc | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) Summary over all repositories: 3 files changed, 29 insertions(+), 0 deletions(-) -- Generated by git-murpp 0.8.1