Gargi-jais11 opened a new pull request, #8972:
URL: https://github.com/apache/ozone/pull/8972
## What changes were proposed in this pull request?
This ticket fixes inconsistencies in **VolumeDataDensity calculations**
between SCM and DN causing misleading reports.
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 (on SCM side in DiskBalancerManager ),
EstimatedBytesToMove calculation should be aligned with
DefaultVolumeChoosingPolicy calculation.{}
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) .
## What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-13611
## How was this patch tested?
passed existing test.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org
For additional commands, e-mail: issues-h...@ozone.apache.org
