Skip to content

Conversation

@sodonnel
Copy link
Contributor

What changes were proposed in this pull request?

After some discussion with István Fajth and Siddharth Wagle we believe that the change in HDDS-5153 should be reverted.

If a DN starts decommissioning or maintenance, but goes dead before it completes the process, then the node is moved back to a state of IN_SERVICE and DEAD by the decommission monitor when it notices it has become dead. This is because decommission should gracefully remove the node, but it goes dead first, we may not be able to replicate its containers. In this case decommission effectively fails.

In HDDS-5153, we decided that if a node is already dead and you decommission it, it should immediately move to DECOMMISSIONED. However that is not really consistent with the above behaviour.

Also, there is no real value in decommissioning a dead node - it does not do anything except adjust its state in SCM.

To keep things consistent, I propose we revert HDDS-5153 so starting decommission on a dead node will work the same as when a node goes dead part way through decommission. In both cases the node will end up as IN_SERVICE + DEAD.

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-5274

How was this patch tested?

Existing tests

@sodonnel sodonnel requested a review from fapifta May 25, 2021 16:47
Copy link
Contributor

@fapifta fapifta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM +1

@sodonnel sodonnel merged commit 8c1de61 into apache:master Jun 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants