[
https://issues.apache.org/jira/browse/HDDS-4989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-4989:
---------------------------------
Labels: pull-request-available (was: )
> Decommission CLI should return details of nodes which fail
> ----------------------------------------------------------
>
> Key: HDDS-4989
> URL: https://issues.apache.org/jira/browse/HDDS-4989
> Project: Apache Ozone
> Issue Type: Improvement
> Components: SCM, SCM Client
> Reporter: Stephen O'Donnell
> Assignee: Stephen O'Donnell
> Priority: Major
> Labels: pull-request-available
>
> With the current decommission / recommission / maintenance mode commands, you
> can pass a list of hosts to perform the operation on. If any of these hosts
> fail to enter the decommission / maintenance workflow, the command gives no
> feedback about the error. Some of the hosts can silently fail and the only
> way to know is to inspect the SCM log.
> The most common way a host can fail, is if a node which is undergoing
> maintenance is instructed to go to decommission and vice versa as this is a
> transition which is not allowed.
> This change will allow any failed nodes to feed back to the client. If the
> client detects that any of the nodes have failed, details will be written to
> stderr and the command exit code will be non-zero.
> Note that even though the exit code is non-zero, the command may have
> partially worked.
> Also note that the errors which are fed back are only around transitioning
> the node into the admin workflow - it is still possible for it to fail later
> for other reasons which will not be fed back to the client. This is because
> the client does not wait for the process to complete, but exits after
> confirmation the command has been processed by scm.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
