[GitHub] [hadoop-ozone] arp7 edited a comment on pull request #1149: HDDS-3878. Make OMHA serviceID optional if one (but only one) is defined in the config

[GitBox <gi...@apache.org>]

arp7 edited a comment on pull request #1149:
URL: https://github.com/apache/hadoop-ozone/pull/1149#issuecomment-655721161


   > If the user has both remote and local (or multiple federated cluster) it means that we have two service ids.
   We want to support client-less config of HA eventually (using DNS for example). In that case we cannot look at the client side configs to know how many clusters/services there are.
   
   This should be an inconvenience only for manually types o3fs paths. For programmatic usage it shouldn't be such a big deal right? I feel it was a mistake in HDFS to not require fully qualified paths for HA. It made the adoption of viewfs/federation more difficult.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org