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 659BC1FF13F for ; Thu, 09 Apr 2026 13:43:42 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 28A4427CC; Thu, 9 Apr 2026 13:43:23 +0200 (CEST) From: Daniel Kral To: pve-devel@lists.proxmox.com Subject: [PATCH docs 16/18] ha-manager: crs: add dynamic load scheduler Date: Thu, 9 Apr 2026 13:41:42 +0200 Message-ID: <20260409114224.323102-17-d.kral@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260409114224.323102-1-d.kral@proxmox.com> References: <20260409114224.323102-1-d.kral@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1775734880312 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.081 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: NOWV5RNZIGNSQZAZH5W2HZDVZHZQDQGY X-Message-ID-Hash: NOWV5RNZIGNSQZAZH5W2HZDVZHZQDQGY X-MailFrom: d.kral@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: For pve-ha-manager >= 5.2.0, the HA Manager also has a dynamic-load scheduler mode. Signed-off-by: Daniel Kral --- ha-manager.adoc | 21 +++++++++++++++------ 1 file changed, 15 insertions(+), 6 deletions(-) diff --git a/ha-manager.adoc b/ha-manager.adoc index 624c403..4162071 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -1453,6 +1453,14 @@ Static usage information from active guests on each node is used to choose the best-fitting node for an HA resource. This includes the configured CPU and memory quotas for the active guests. +[[_dynamic_scheduler]] +Dynamic-Load Scheduler +^^^^^^^^^^^^^^^^^^^^^^ + +Dynamic usage information from active guests on each node is used to choose the +best-fitting node for an HA resource. This includes the average CPU and memory +usage as well as the configured CPU and memory quotas for the active guests. + [[ha_manager_crs_scheduling_points]] CRS Scheduling Points ~~~~~~~~~~~~~~~~~~~~~ @@ -1499,8 +1507,9 @@ the current node, the HA resource will be migrate to the selected node. For the xref:_basic_scheduler[basic scheduler mode], the node with the least resources count is considered as the best suited node. -For the xref:_static_scheduler[static-load scheduler mode], each node in turn -is considered as if the HA resource was already running on it, using CPU and +For the xref:_static_scheduler[static] and +xref:_dynamic_scheduler[dynamic-load scheduler mode], each node in turn is +considered as if the HA resource was already running on it, using CPU and memory usage from the associated guest configuration. Then for each such alternative, CPU and memory usage of all nodes are considered, with memory being weighted much more, because it's a truly limited resource. For both, CPU @@ -1512,10 +1521,10 @@ considered. This setting can be enabled with the CRS option `ha-rebalance-on-start` in the web interface under `Datacenter` -> `Options` -> `Cluster Resource Scheduling`. -IMPORTANT: For the static-load scheduler mode, this functionality is still in -technology preview. The more HA resources the more possible combinations there -are, so it's currently not recommended to use it if you have thousands of HA -resources. +IMPORTANT: For the static-load and dynamic-load scheduler mode, this +functionality is still in technology preview. The more HA resources the more +possible combinations there are, so it's currently not recommended to use it if +you have thousands of HA resources. ifdef::manvolnum[] include::pve-copyright.adoc[] -- 2.47.3