[
https://issues.apache.org/jira/browse/HDDS-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lisheng Sun updated HDDS-3667:
------------------------------
Summary: If we gracefully stop datanode it would be better to notify scm
and recon (was: If we gracefully stop datanode it would be better to notify
scm and recon to unregister)
> If we gracefully stop datanode it would be better to notify scm and recon
> --------------------------------------------------------------------------
>
> Key: HDDS-3667
> URL: https://issues.apache.org/jira/browse/HDDS-3667
> Project: Hadoop Distributed Data Store
> Issue Type: New Feature
> Components: Ozone Datanode, Ozone Recon, SCM
> Affects Versions: 0.6.0
> Reporter: maobaolong
> Assignee: Lisheng Sun
> Priority: Minor
> Labels: pull-request-available
>
> if you execute `bin/ozone --daemon stop datanode`, datanode would be better
> if it handle the signal and the stop dn request to scm, then scm update
> datanode state to dead.
> It would be better if you provide a admin cli tool to support remove datanode
> manually.
> {code:bash}
> ozone admin datanode remove <UUID>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]