Gargi Jaiswal created HDDS-14883:
------------------------------------
Summary: ContainerBalancerStatus shows 0GB due to incorrect field
mapping
Key: HDDS-14883
URL: https://issues.apache.org/jira/browse/HDDS-14883
Project: Apache Ozone
Issue Type: Bug
Reporter: Gargi Jaiswal
“{*}Max Size to Move per Iteration{*}” showing 0GB – bug
The “{*}Max Size to Move per Iteration{*}” value was coming from the wrong
field (Max Datanodes % instead of Max Size to Move), so it often displayed 0GB.
This needs to be fixed in{color:#de350b}
{{ContainerBalancerStatusSubcommand.java}}{color}: so that the status output
should use {color:#de350b}{{getSizeMovedMaxPerIteration()}}{color} instead of
{color:#de350b}{{getDatanodesInvolvedMaxPercentagePerIteration().}}
{color}
{{https://github.com/apache/ozone/blob/2ebb1509771e496acd9246d3c7e552d78f2aaa67/hadoop-ozone/cli-admin/src/main/java/org/apache/hadoop/hdds/scm/cli/ContainerBalancerStatusSubcommand.java#L128-L131}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
