[
https://issues.apache.org/jira/browse/HDDS-14110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gargi Jaiswal updated HDDS-14110:
---------------------------------
Description:
This ticket resolves the bugs found out :
* {{EstimatedBytesToMoved}} and {{EstimatedTimeLeft}} should not be shown up
if no container movement happens.
* Improve threshold validation error message. When running the DiskBalancer
update command with a threshold value of {*}100.0{*}, the operation fails on
all datanodes with the following error:
{code:java}
bash> ozone admin datanode diskbalancer update -t 100.0 --in-service-datanodes
Error on node [DN-1]: Threshold must be a percentage(double) in the range 0 to
100.{code}
A threshold of *0* means any deviation from ideal usage (even 0.01%) triggers
container movement
- This leads to excessive and continuous balancing operations and results in
unnecessary I/O overhead and resource consumption
A Threshold value can never be 100.0% as it would mean allow moving 100% of a
disk's contents, effectively emptying one disk.
*Suggested improvement:*
Rather the error message should clarify that 0 and 100 is excluded. The
validation is being updated to exclude 0, requiring threshold to be in
the range (0, 100) exclusive.
new error msg:
{code:java}
Error on node [DN-1]: Threshold must be a percentage(double) in the range 0 to
100 both exclusive.{code}
was:
This ticket resolves the bugs found out :
* {{EstimatedBytesToMoved}} and {{EstimatedTimeLeft}} should not be shown up
if no container movement happens.
* Improve threshold validation error message. When running the DiskBalancer
update command with a threshold value of {*}100.0{*}, the operation fails on
all datanodes with the following error:
{code:java}
bash> ozone admin datanode diskbalancer update -t 100.0 --in-service-datanodes
Error on node [DN-1]: Threshold must be a percentage(double) in the range 0 to
100.{code}
*Suggested improvement:*
A Threshold value can never be 100.0% as it would mean allow moving 100% of a
disk's contents, effectively emptying one disk. Rather the error message should
clarify that 100 is excluded.
new error msg:
{code:java}
Error on node [DN-1]: Threshold must be a percentage(double) in the range 0 to
100 both exclusive.{code}
> [DiskBalancer] Show EstimatedBytesToMove only during active balancing and
> improve threshold check message
> ---------------------------------------------------------------------------------------------------------
>
> Key: HDDS-14110
> URL: https://issues.apache.org/jira/browse/HDDS-14110
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Gargi Jaiswal
> Assignee: Gargi Jaiswal
> Priority: Minor
>
> This ticket resolves the bugs found out :
> * {{EstimatedBytesToMoved}} and {{EstimatedTimeLeft}} should not be shown up
> if no container movement happens.
> * Improve threshold validation error message. When running the DiskBalancer
> update command with a threshold value of {*}100.0{*}, the operation fails on
> all datanodes with the following error:
> {code:java}
> bash> ozone admin datanode diskbalancer update -t 100.0 --in-service-datanodes
> Error on node [DN-1]: Threshold must be a percentage(double) in the range 0
> to 100.{code}
> A threshold of *0* means any deviation from ideal usage (even 0.01%) triggers
> container movement
> - This leads to excessive and continuous balancing operations and results in
> unnecessary I/O overhead and resource consumption
> A Threshold value can never be 100.0% as it would mean allow moving 100% of a
> disk's contents, effectively emptying one disk.
> *Suggested improvement:*
> Rather the error message should clarify that 0 and 100 is excluded. The
> validation is being updated to exclude 0, requiring threshold to be in
> the range (0, 100) exclusive.
> new error msg:
> {code:java}
> Error on node [DN-1]: Threshold must be a percentage(double) in the range 0
> to 100 both exclusive.{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
