[
https://issues.apache.org/jira/browse/HDDS-13667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18023509#comment-18023509
]
Gargi Jaiswal commented on HDDS-13667:
--------------------------------------
As discussed with [~sammichen] for the first part the root cause is same as of
this issue https://issues.apache.org/jira/browse/HDDS-13602 . This ticket will
only resolve the other part of the ticket, i.e,
Currently DiskBalancer start, stop and update command is send only to
IN_SERVICE_HEALTHY DN but user has no info about this so improve cli output
message to show as below:
{code:java}
bash-5.1$ ozone admin datanode diskbalancer start -t 0.0001 -a
Start DiskBalancer on datanode(s):
All datanodes which are IN_SERVICE and HEALTHY.
{code}
> [DiskBalancer] Improve container write locks & DiskBalancer CLI message for
> failed commands
> -------------------------------------------------------------------------------------------
>
> Key: HDDS-13667
> URL: https://issues.apache.org/jira/browse/HDDS-13667
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Gargi Jaiswal
> Assignee: Gargi Jaiswal
> Priority: Major
>
> # We should have {*}container write lock{*}, as some parallel deletion of
> blocks, can delete from old, and present in new container ... resulting in
> orphan blocks. This might be required since start of copy container.
> # Currently DiskBalancer *start, stop* and *update* command is send only to
> *IN_SERVICE_HEALTHY* DN but user has no info about this so improve cli output
> message to show as below:
> {code:java}
> bash-5.1$ ozone admin datanode diskbalancer start -t 0.0001 -a
> Start DiskBalancer on datanode(s):
> All datanodes which are IN_SERVICE and HEALTHY. {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]
