[
https://issues.apache.org/jira/browse/HDDS-8749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729209#comment-17729209
]
Attila Doroszlai commented on HDDS-8749:
----------------------------------------
[~dalamar33], when using Ozone OM HA, filesystem URLs should include the OM
service ID instead of a single OM host address.
Hope this doc helps:
https://ozone.apache.org/docs/1.3.0/feature/om-ha.html#configuration
> [Hadoop OFS] HDFS commands fail when not set as the leader of OMHA
> ------------------------------------------------------------------
>
> Key: HDDS-8749
> URL: https://issues.apache.org/jira/browse/HDDS-8749
> Project: Apache Ozone
> Issue Type: Bug
> Components: OFS, OM HA
> Affects Versions: 1.3.0
> Environment: OS: Red Hat 8
> Reporter: David Ayres
> Priority: Minor
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
