Gargi-jais11 opened a new pull request, #8150: URL: https://github.com/apache/ozone/pull/8150
## What changes were proposed in this pull request? As VolumeDensity is already covered by report sub command, we will show bytesMoved (bytesBalanced) in status command. Besides, the meaning of VolumeDensity is clear to end user, but the real value indicating is not that straight forward. Use the estimated pending move size([HDDS-12437](https://issues.apache.org/jira/browse/HDDS-12437)) will help user to clearly understand how much data size need to move. And this bytesMoved is also a straight forward value, indicating the work disk balancer has done. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-12546 ## How was this patch tested? Tested manually by running docker cluster locally. ``` bash-5.1$ ozone admin datanode diskbalancer status Status result: Datanode BalancedBytes Status Threshold(%) BandwidthInMB Threads SuccessMove FailureMove EstBytesToMove(MB) EstTimeLeft(min) ozone-datanode-1.ozone_default 8082423808 RUNNING 0.0002 10 5 7 3 419 1 ozone-datanode-2.ozone_default 9525264384 RUNNING 0.0002 10 5 8 2 812 2 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]
