Gargi-jais11 opened a new pull request, #9111: URL: https://github.com/apache/ozone/pull/9111
## What changes were proposed in this pull request? Suppose density of disk is, 1%, 2%, 8%, 9% ==> this will be treated as disk unbalanced, but disk is under utilised. Triggering disk balancer in this scenario is not expected. Min-Disk-Density-For-balancer >= 60% for running balancer can be there to avoid this. **Solution:** Add a new configuration `hdds.datanode.disk.balancer.min.source.volume.density` with default value **60%**, means a volume is considered as source volume only if has utilisation greater than or equal to 60%. This prevents the bove scenario of running diskBalancer for all under utilised disks which seems to be imbalanced. Thus saving unnecessary data movement. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-13697 ## How was this patch tested? Updated exiting UT. Tested on docker : ``` bash-5.1$ ozone admin datanode diskbalancer start -t 0.0001 -m 5 -a Start DiskBalancer on datanode(s): All datanodes bash-5.1$ ozone admin datanode diskbalancer status Status result: Datanode Status Threshold(%) BandwidthInMB Threads SuccessMove FailureMove BytesMoved(MB) EstBytesToMove(MB) EstTimeLeft(min) ozone-datanode-1.ozone_default STOPPED 0.0001 10 5 0 0 0 0 0 ozone-datanode-5.ozone_default RUNNING 0.0001 10 5 0 0 0 0 0 ozone-datanode-2.ozone_default RUNNING 0.0001 10 5 0 0 0 0 0 ozone-datanode-3.ozone_default STOPPED 0.0001 10 5 0 0 0 0 0 ozone-datanode-4.ozone_default STOPPED 0.0001 10 5 0 0 0 0 0 Note: Estimated time left is calculated based on the estimated bytes to move and the configured disk bandwidth. ``` -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
