aryangupta1998 opened a new pull request, #4074: URL: https://github.com/apache/ozone/pull/4074
## What changes were proposed in this pull request? When we add a new OM node right after decommissioning, the OM process on the new node gets terminated immediately on the restart. The new OM node is unable to join the ratis ring. This is because OM applies all the previous transactions which also includes the transaction to decommission(removal of a node from peer list) which causes termination of the newly added OM process node. The assumption here is that the OM node id of the newly added node is the same as that of the decommissioned node. Problem: Decommissioning operation (Update Peer List) is replayed from the Raft log when the new node is bootstrapped. If we use the same OM ID (decommissioned OM ID) for the newly added node, during Raft Log replay OzoneManager thinks that the current node (new node) is being decommissioned and it stops the bootstrap process. The fix here is to not stop the OM process, only display the log to warn the user that the newly added OM Id is the same as the one decommissioned. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-7584 ## How was this patch tested? Tested Manually -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
