[
https://issues.apache.org/jira/browse/HDDS-7088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-7088:
---------------------------------
Labels: pull-request-available (was: )
> OM incorrectly detects SCM Ratis Group ID when OM and SCM are colocated with
> same Ratis storage directory
> ---------------------------------------------------------------------------------------------------------
>
> Key: HDDS-7088
> URL: https://issues.apache.org/jira/browse/HDDS-7088
> Project: Apache Ozone
> Issue Type: Bug
> Components: OM HA, SCM HA
> Affects Versions: 1.2.1
> Reporter: Ethan Rose
> Assignee: Navin Kumar
> Priority: Major
> Labels: pull-request-available
>
> When OM and SCM are colocated and ozone.om.ratis.storage.dir and
> ozone.scm.ha.ratis.storage.dir are set to the same directory, the OM will
> incorrectly detect SCM's Ratis group ID and think that were was an erroneous
> change to the OM service ID.
> {code}
> 22022-07-21 12:57:24,691 ERROR
> org.apache.hadoop.ozone.om.OzoneManagerStarter: OM start failed with exception
> java.io.IOException: Ratis group Dir on disk scm does not match with
> RaftGroupID7f6848f2-63c2-3ce4-a1d2-9e88065dfcc3 generated from service id
> ozone1. Looks like there is a change to ozone.om.service.ids value after the
> cluster is setup. Currently change to this value is not supported.
> {code}
> This Jira is to support setting the two configurations to the same directory
> when OM and SCM are colocated while still maintaining the OM service ID check.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
