[
https://issues.apache.org/jira/browse/HDDS-13667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sammi Chen updated HDDS-13667:
------------------------------
Fix Version/s: 2.2.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> [DiskBalancer] Improve 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
> Labels: pull-request-available
> Fix For: 2.2.0
>
>
> # 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) which are IN_SERVICE and HEALTHY. {code}
> When start, stop and update command is sent to a specific DN which is not
> {*}IN_SERVICE_HEALTHY{*}, command should be rejected same as when sent to all
> DN.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
