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 698EB1FF17E for ; Thu, 16 Oct 2025 13:33:05 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 935F711102; Thu, 16 Oct 2025 13:33:24 +0200 (CEST) Message-ID: <6b51b9d2-bdec-4b60-8594-07483c9c77f9@proxmox.com> Date: Thu, 16 Oct 2025 13:33:20 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Proxmox VE development discussion , Daniel Kral References: <20250930142021.366529-1-d.kral@proxmox.com> <20250930142021.366529-7-d.kral@proxmox.com> Content-Language: en-US From: Fiona Ebner In-Reply-To: <20250930142021.366529-7-d.kral@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1760614397530 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.021 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [manager.pm] Subject: Re: [pve-devel] [PATCH ha-manager 3/9] manager: remove redundant add_service_usage_to_node from next_state_recovery 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" Am 30.09.25 um 4:20 PM schrieb Daniel Kral: > Since 5c2eef4b ("account service to source and target during move") a > moving HA resource's load is accounted for on the source and target > nodes. > > A HA resource is in the 'recovery' state after a successfully fenced > node and its primary goal becomes to find a recovery node. As soon as a > recovery node is found, the HA resource is moved there. As the previous > node was fenced, there is only load on the recovery node. > > The add_service_usage_to_node(...) is redundant at this point as the > subsequent call to change_service_state(...) to either the 'started' or > 'request_stop' state will call recompute_online_node_usage(...) and make > the changes to $online_node_usage be discarded immediately. This was done with the plan to make it more granular in mind, explicitly not relying on a particular recompute_online_node_usage() call. I guess the necessary calculation will still be covered by change_service_state() at the end of the series? If yes, please mention that in the commit message here and take a > Signed-off-by: Daniel Kral Reviewed-by: Fiona Ebner > --- > src/PVE/HA/Manager.pm | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/src/PVE/HA/Manager.pm b/src/PVE/HA/Manager.pm > index f69a7fe9..6afc9250 100644 > --- a/src/PVE/HA/Manager.pm > +++ b/src/PVE/HA/Manager.pm > @@ -1321,8 +1321,6 @@ sub next_state_recovery { > $fence_recovery_cleanup->($self, $sid, $fenced_node); > > $haenv->steal_service($sid, $sd->{node}, $recovery_node); > - $self->{online_node_usage}->add_service_usage_to_node($recovery_node, $sid, $recovery_node); > - $self->{online_node_usage}->add_service_node($sid, $recovery_node); > > # NOTE: $sd *is normally read-only*, fencing is the exception > $cd->{node} = $sd->{node} = $recovery_node; _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel