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

Ivan Andika updated HDDS-12389:
-------------------------------
    Description: 
Currently, we allow datanode to be stopped anytime using "ozone --daemon stop 
datanode" command regardless even if the datanode is still active (e.g. there 
is still an active write pipeline on the datanode). This affects user writes 
since the pipeline is still being used. It might also trigger unnecessary 
container migrations since the SCM might think that the datanode is DEAD 
instead of just IN_MAINTENANCE.

I propose that by default datanode can only be stopped by administrator if it 
is either IN_MAINTENANCE or DECOMMISSIONED. If the administrator wants to stop 
it forcefully, he/she needs to specify the --force flag ("ozone --daemon stop 
--force").

  was:
Currently, we allow datanode to be stopped anytime using "ozone --daemon stop 
datanode" command regardless even if the datanode is still active (e.g. there 
is still an active write pipeline on the datanode). 

I propose that by default datanode can only be stopped by administrator if it 
is either IN_MAINTENANCE or DECOMMISSIONED. If the administrator wants to stop 
it forcefully, he/she needs to specify the --force flag ("ozone --daemon stop 
--force").


> Disallow stopping active datanode
> ---------------------------------
>
>                 Key: HDDS-12389
>                 URL: https://issues.apache.org/jira/browse/HDDS-12389
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: Ozone Datanode
>            Reporter: Ivan Andika
>            Assignee: Ivan Andika
>            Priority: Major
>
> Currently, we allow datanode to be stopped anytime using "ozone --daemon stop 
> datanode" command regardless even if the datanode is still active (e.g. there 
> is still an active write pipeline on the datanode). This affects user writes 
> since the pipeline is still being used. It might also trigger unnecessary 
> container migrations since the SCM might think that the datanode is DEAD 
> instead of just IN_MAINTENANCE.
> I propose that by default datanode can only be stopped by administrator if it 
> is either IN_MAINTENANCE or DECOMMISSIONED. If the administrator wants to 
> stop it forcefully, he/she needs to specify the --force flag ("ozone --daemon 
> stop --force").



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to