[HDDS-8749] [Hadoop OFS] HDFS commands fail when not set as the leader of OMHA

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.3.0
• Component/s: OFS, OM HA

Environment

OS: Red Hat 8

• Assignee: Unassigned
• Reporter: David Ayres
• Created: 02/Jun/23 19:48
• Updated: 05/Jun/23 18:50
• Resolved: 05/Jun/23 18:41

Description

When setting the defaultFS in Hadoop's core-site.xml it seems you are only allowed to declare one OM node, but if the node declared is not the leader it fails with the following error:

INFO retry.RetryInvocationHandler: com.google.protobuf.ServiceException: org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ozone.om.exceptions.OMNotLeaderException): OM:om1 is not the leader. Could not determine the leader node.

 

, while invoking $Proxy13.submitRequest over nodeId=null,nodeAddress=ddl07oom01.vuhl.root.mrc.local:9862 after 1 failover attempts. Trying to failover after sleeping for 4000ms. Current retry count: 1.

 

HDFS commands only work when declaring the leader, but that would defeat the purpose of HA. As if the OM node were to fail over HDFS commands would cease to work.

 

There also does not seem to be any documentation on how HA works with OFS/O3FS as of yet and I am not sure if this is a feature in the works or not.

Issue Links

• relates to: HDDS-8754 Test Hadoop compatibility in Ozone HA environment