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 C977E1FF185 for ; Mon, 4 Aug 2025 16:11:09 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 87F0633525; Mon, 4 Aug 2025 16:12:40 +0200 (CEST) From: Daniel Kral To: pve-devel@lists.proxmox.com Date: Mon, 4 Aug 2025 16:11:41 +0200 Message-ID: <20250804141204.207216-3-d.kral@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250804141204.207216-1-d.kral@proxmox.com> References: <20250804141204.207216-1-d.kral@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1754316709276 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.014 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 Subject: [pve-devel] [PATCH docs 3/5] ha: rules: document crs behavior for split positive resource affinity X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Signed-off-by: Daniel Kral --- ha-manager.adoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/ha-manager.adoc b/ha-manager.adoc index 5d75287..e18a14d 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -787,6 +787,11 @@ HA resources `vm:101` and `vm:102` are each in a positive resource affinity rule, then it is the same as if `vm:100`, `vm:101` and `vm:102` would have been in a single positive resource affinity rule. +NOTE: If the HA resources of a positive resource affinity rule are currently +running on different nodes, the CRS will move the HA resources to the node, +where most of them are running already. If there is a tie in the HA resource +count, the node with the alphabetically first name is chosen. + However, suppose there are computationally expensive, and/or distributed programs running on the HA resources `vm:200` and `ct:300`, for example, sharded database instances. In that case, running them on the same node could -- 2.47.2 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel