Gargi Jaiswal created HDDS-13611:
------------------------------------
Summary: [DiskBalancer] Inconsistent VolumeDataDensity
calculations between SCM and DN causing misleading reports and incorrect
EstBytesToMove
Key: HDDS-13611
URL: https://issues.apache.org/jira/browse/HDDS-13611
Project: Apache Ozone
Issue Type: Sub-task
Reporter: Gargi Jaiswal
Assignee: Gargi Jaiswal
This ticket fixes inconsistencies in *VolumeDataDensity* calculations between
*SCM* and *DN*
# Although *volumeDataDensity* for the datanode is *0.0* still it is started
and showing containers moved.
# *Estimated bytes moved and estimated time left* is 0 although it is moving
containers.
*Proposed Solution:*
*VolumeDataDensity* calculation should be done on the DN side so that it
considers all the ongoing operations and then correctly report it to the SCM.
And this VolumeDataDensity calculation should be *standAlone utility on
datanode side that can calculate VolumeDataDensity regardless of diskbalancer
state (stopped or running)* .
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
