[HDDS-7088] OM incorrectly detects SCM Ratis Group ID when OM and SCM are colocated with same Ratis storage directory

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.1
• Fix Version/s: 1.3.0
• Component/s: OM HA, SCM HA
• Labels: pull-request-available
• Assignee: Navin Kumar
• Reporter: Ethan Rose
• Created: 03/Aug/22 19:14
• Updated: 12/Oct/22 07:49
• Resolved: 12/Oct/22 07:37

Description

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.

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.

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.

Issue Links

• relates to: HDDS-7103 Ratis log storage directories unchecked causing unhandled exception on datanode restart
• links to: GitHub Pull Request #3809