You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Nandakumar (Jira)" <ji...@apache.org> on 2022/12/23 07:21:00 UTC

[jira] [Resolved] (HDDS-7584) Addition of new OM node expels itself from the Ratis ring after restart

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

Nandakumar resolved HDDS-7584.
------------------------------
    Fix Version/s: 1.4.0
       Resolution: Fixed

> Addition of new OM node expels itself from the Ratis ring after restart 
> ------------------------------------------------------------------------
>
>                 Key: HDDS-7584
>                 URL: https://issues.apache.org/jira/browse/HDDS-7584
>             Project: Apache Ozone
>          Issue Type: Bug
>            Reporter: Aryan Gupta
>            Assignee: Aryan Gupta
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.4.0
>
>
> 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.
> cc  [~sshenoy] [~nanda]



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org