Gargi Jaiswal created HDDS-14866:
------------------------------------
Summary: Enhance DiskBalancer Report to show individual volume's
density
Key: HDDS-14866
URL: https://issues.apache.org/jira/browse/HDDS-14866
Project: Apache Ozone
Issue Type: Sub-task
Reporter: Gargi Jaiswal
Assignee: Gargi Jaiswal
The DiskBalancer report today shows only:
{code:java}
ozone admin datanode diskbalancer report --in-service-datanodes
Report result:
Datanode VolumeDensity
dn-hostname-3 (10.141.248.70:19864) 0.09267551461620249
dn-hostname-1 (10.141.128.135:19864) 0.06619677701803184
dn-hostname-2 (10.141.126.8:19864) 0.026044182616493772{code}
So users see only a single *{{{}aggregate VolumeDensity per datanode{}}},* with
no per-disk breakdown.
According to above report if user wants to run diskbalancer at threshold lower
that 10% say at 5% it interprets that diskbalancer will start on *DN-3 and
DN-1.* But it does not start and creates confusion that diskbalancer is not
working correctly.
This is because in reality this threshold value checks wether each volumes
utilisation is above or below or within the range.
*Proposed Solution:*
We should also show each volume's density along with the details of each
volumes utilisation and pre-allocated container bytes
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
