[jira] [Updated] (HDDS-3667) If we gracefully stop datanode it would be better to notify scm and recon

["Ethan Rose (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDDS-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ethan Rose updated HDDS-3667:
-----------------------------
    Target Version/s: 1.3.0  (was: 1.2.0)

I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.

If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.

> 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: Apache Ozone
>          Issue Type: New Feature
>          Components: Ozone Datanode, Ozone Recon, SCM
>    Affects Versions: 1.0.0
>            Reporter: Baolong Mao
>            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: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org