[
https://issues.apache.org/jira/browse/HDDS-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Elek resolved HDDS-3097.
-------------------------------
Resolution: Duplicate
I accidentally created a duplicate of this and created a patch:
HDDS-3878
It seems that we agree that everything should work as before if only one
serviceid is defined for omha.
> Fallback to ozone.om.address if suffixed key is not defined
> -----------------------------------------------------------
>
> Key: HDDS-3097
> URL: https://issues.apache.org/jira/browse/HDDS-3097
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: OM HA, Ozone Manager
> Reporter: Hanisha Koneru
> Assignee: Hanisha Koneru
> Priority: Major
>
> Currently, if ozone.om.service.ids is defined but either
> ozone.om.nodes.<serviceID> or ozone.om.address<serviceID>.<nodeID> keys are
> not defined, then OM throws OzoneIllegalArgumentException.
> For a single node OM cluster, we should always fallback to ozone.om.address
> (even if service id is defined).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
