You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Sreeja (Jira)" <ji...@apache.org> on 2026/06/24 10:08:00 UTC
[jira] [Updated] (HDDS-15654) Remove unused withinThresholdUtilizedNodes list from ContainerBalancerTask
[ https://issues.apache.org/jira/browse/HDDS-15654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sreeja updated HDDS-15654:
--------------------------
Summary: Remove unused withinThresholdUtilizedNodes list from ContainerBalancerTask (was: withinThresholdUtilizedNodes never cleared between iterations )
> Remove unused withinThresholdUtilizedNodes list from ContainerBalancerTask
> --------------------------------------------------------------------------
>
> Key: HDDS-15654
> URL: https://issues.apache.org/jira/browse/HDDS-15654
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Ashish Kumar
> Assignee: Sreeja
> Priority: Major
> Labels: container-balancer
>
> In ContainerBalancerTask, withinThresholdUtilizedNodes list is populated in initializeIteration() but never used for source/target selection, since getPotentialSources() / getPotentialTargets() only return over/under nodes. There are TODOs to include within threshold nodes as candidates, but that was never implemented.
> Using within threshold nodes as balancing candidates is not needed as the balancer's threshold configuration already controls participation. If a within threshold node should participate, operators can tighten the threshold to reclassify it as over- or under utilized.
> Fix: Remove withinThresholdUtilizedNodes list and the related TODOs. No change to current balancer behavior.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org