[
https://issues.apache.org/jira/browse/HDDS-8872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-8872:
---------------------------------
Labels: pull-request-available (was: )
> New bootstrapped OM shouldn’t shutdown if ratis applies previous transactions
> -----------------------------------------------------------------------------
>
> Key: HDDS-8872
> URL: https://issues.apache.org/jira/browse/HDDS-8872
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Manager
> Reporter: Aryan Gupta
> Assignee: Aryan Gupta
> Priority: Major
> Labels: pull-request-available
>
> When we decommission an OM node and then try to bootstrap a new OM node then
> ratis try to apply previous transactions and the call goes to
> "addOMNodeToPeers()" of OzoneManager.java which results in throwing off an
> exception as it's not able to find the details of the decommissioned node in
> the conf which is correct as node doesn’t exist as an OM now. So, we are
> changing the exception to a warning message so that process flow shouldn't
> stop and newly bootstrapped OM doesn’t get shut down.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
