[
https://issues.apache.org/jira/browse/HDFS-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189321#comment-13189321
]
Aaron T. Myers commented on HDFS-2367:
--------------------------------------
bq. In theory this should also support a non-federated configuration by just
specifying dfs.ha.namenodes and then dfs.namenode.rpc-address.nn1, etc.. have
you tested that manually?
I talked to Todd about this, and we concluded this isn't actually true. Some of
the server side configuration is implemented such that it could deal with a
null value for nameServiceId, but the configuration is necessary for client
side failover to be configured correctly.
bq. Can you either leave this TODO in there, or file a JIRA for it?
Filed: HDFS-2811
> HA: Enable the configuration of multiple HA cluster addresses
> -------------------------------------------------------------
>
> Key: HDFS-2367
> URL: https://issues.apache.org/jira/browse/HDFS-2367
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, hdfs client
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Fix For: HA branch (HDFS-1623)
>
> Attachments: HDFS-2367-HDFS-1623.patch, HDFS-2367-HDFS-1623.patch
>
>
> Todd pointed out this issue with the current patch posted for HDFS-1623. It
> seems like the solution would be to replace "dfs.ha.namenode.addresses" with
> something like "dfs.ha.namenode.addresses.<logical-uri>", so as to be able to
> support configuring the addresses of multiple HA clusters.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
