From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 3/5] ha: rules: document crs behavior for split positive resource affinity
Date: Mon, 4 Aug 2025 16:11:41 +0200 [thread overview]
Message-ID: <20250804141204.207216-3-d.kral@proxmox.com> (raw)
In-Reply-To: <20250804141204.207216-1-d.kral@proxmox.com>
Signed-off-by: Daniel Kral <d.kral@proxmox.com>
---
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
next prev parent reply other threads:[~2025-08-04 14:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 14:11 [pve-devel] [PATCH docs 1/5] ha: affinity rules: simplify overly verbose rule conflicts and errors section Daniel Kral
2025-08-04 14:11 ` [pve-devel] [PATCH docs 2/5] ha: rules: update about mixed usage of node and resource affinity rules Daniel Kral
2025-08-04 15:09 ` Hannes Duerr
2025-08-05 7:15 ` Daniel Kral
2025-08-04 14:11 ` Daniel Kral [this message]
2025-08-05 7:42 ` [pve-devel] [PATCH docs 3/5] ha: rules: document crs behavior for split positive resource affinity Michael Köppl
2025-08-05 7:50 ` Daniel Kral
2025-08-04 14:11 ` [pve-devel] [PATCH docs 4/5] ha: mark ha groups as deprecated and note migration to node affinity rules Daniel Kral
2025-08-04 14:11 ` [pve-devel] [PATCH docs 5/5] ha: replace in-text references to ha groups with ha rules Daniel Kral
2025-08-04 15:24 ` Hannes Duerr
2025-08-05 7:39 ` Daniel Kral
2025-08-05 7:41 ` Michael Köppl
2025-08-05 7:47 ` [pve-devel] [PATCH docs 1/5] ha: affinity rules: simplify overly verbose rule conflicts and errors section Michael Köppl
2025-08-05 8:01 ` [pve-devel] applied: " Daniel Kral
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250804141204.207216-3-d.kral@proxmox.com \
--to=d.kral@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.