Ivan Andika created HDDS-15025:
----------------------------------
Summary: Bootstrapped OM node is different than the Ratis
configuration
Key: HDDS-15025
URL: https://issues.apache.org/jira/browse/HDDS-15025
Project: Apache Ozone
Issue Type: Bug
Reporter: Ivan Andika
Assignee: Ivan Andika
We encountered issues where the bootstrapped OM returned in getServiceList
("ozone admin om roles") is different than the one in Ratis configuration.
Reproduction (let's use newOmNode as the OM node ID of the bootstrapped OM)
# Start all existing OM with wrong newOmNode node address configuration
# Copy the wrong configuration to another file (e.g. wrong-configuration.xml)
# Correct the new ozone-site.xml
# Bootstrap the new OM newOmNode
# The result is that the Ratis configuration has the correct address, but the
OM node address is wrong
I suspect the issue is that the OM is still using the old wrong configuration
(wrong-configuration.xml) since OM does not set the OzoneManager.configuration
when reloadConfiguration in getOmConfiguration. This creates a mismatch between
Ratis and OM states.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]