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 C892C1FF137 for ; Tue, 03 Mar 2026 18:56:53 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 063F01F145; Tue, 3 Mar 2026 18:57:57 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Friedrich Weber Subject: applied: [PATCH pve-cluster 1/2] corosync: create config: allow setting token coefficient Date: Tue, 3 Mar 2026 18:57:12 +0100 Message-ID: <177256062155.1651319.11505140861282775816.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260212115928.148999-2-f.weber@proxmox.com> References: <20260212115928.148999-1-f.weber@proxmox.com> <20260212115928.148999-2-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: 1772560617740 X-SPAM-LEVEL: Spam detection results: 0 AWL -1.082 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.66 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.968 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.495 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: GUNCCZUCT2YOMBHLH6UXTZWKOKRTROIH X-Message-ID-Hash: GUNCCZUCT2YOMBHLH6UXTZWKOKRTROIH 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 Thu, 12 Feb 2026 12:57:55 +0100, Friedrich Weber wrote: > By default, corosync calculates several timeouts based on the cluster > size, in particular the token timeout, which is a fixed base value > plus the number of nodes (minus 2) multipled by a factor called the > "token coefficient" (with a default of 650ms) [1]. > > New clusters should be created with a lower token coefficient. Thus, > allow to pass a custom token coefficient when creating the > configuration for a new corosync cluster. > > [...] Applied, thanks! [1/2] corosync: create config: allow setting token coefficient commit: a7b1c765b9223a81fb2dc4f072d6a6c095583cda