[
https://issues.apache.org/jira/browse/HDDS-8892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aryan Gupta resolved HDDS-8892.
-------------------------------
Resolution: Not A Problem
As of now after decommissioning an OM node we have to manually clean up the
OM-related data before bootstrapping it which will eventually delete the
VERSION file, hence we'll never run into the issue described in this PR. Hence,
closing the PR.
> OM Node Id from VERSION file should removed after the OM node has been
> decommissioned
> -------------------------------------------------------------------------------------
>
> Key: HDDS-8892
> URL: https://issues.apache.org/jira/browse/HDDS-8892
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Manager
> Reporter: Aryan Gupta
> Assignee: Aryan Gupta
> Priority: Major
> Labels: pull-request-available
>
> OM node id should be removed from the VERSION file after the OM node has been
> decommissioned to avoid OM node Id mismatch in case an ex-OM node is
> bootstrapped again. This can happen when an ex-OM node is bootstrapped, then
> it will be bootstrapped with a new OM node id and the existing VERSION file
> will contain the old OM node id which will cause an OM node id mismatch
> during the bootstrap, therefore we need to remove the OM node id from the
> VERSION file upon successful decommissioning. Also, when an OM is
> bootstrapped if the VERSION file doesn’t exist then it will be created and if
> it exists then a new entry of OM node id will be appended.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
