[
https://issues.apache.org/jira/browse/HDFS-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123255#comment-13123255
]
Aaron T. Myers commented on HDFS-2231:
--------------------------------------
Just realized I said over in HDFS-1973 that I would comment on this JIRA about
client-side conf changes, but it totally slipped my mind.
Anyway, the only change to {{DFSConfigKeys}} in HDFS-1973 was to introduce
{{"dfs.client.failover.proxy.provider"}}, which is a prefix which allows one to
configure a particular implementation of a {{FailoverProxyProvider}} for a
given NN logical URI. That should should be compatible with the changes you've
proposed here, though some of what went in to HDFS-1973 will need a little
adaptation to take advantage of what you've implemented here.
My intention in HDFS-1973 was that the various {{FailoverProxyProvider}}
implementations would be responsible for their own configurations. For example,
a ZK-based {{FailoverProxyProvider}} might need to know the quroum members. So,
the {{ConfiguredFailoverProxyProvider}} introduced by HDFS-1973 introduced the
config parameter "{{dfs.ha.namenode.addresses}}", which is a comma-separated
list of actual (not logical) URIs. This is equivalent to the functionality
introduced by the pair of configuration options {{dfs.namenode.ids}} and
{{dfs.namenode.rpc-address.*}}, introduced this patch, and I like the design
you have here better.
I think it's fine to commit this as-designed now, and then we can fix up
{{ConfiguredFailoverProxyProvider}} once this goes in. I've filed HDFS-2418 to
take care of that.
> Configuration changes for HA namenode
> -------------------------------------
>
> Key: HDFS-2231
> URL: https://issues.apache.org/jira/browse/HDFS-2231
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Fix For: HA branch (HDFS-1623)
>
> Attachments: HDFS-2231.txt, HDFS-2231.txt
>
>
> This jira tracks the changes required for configuring HA setup for namenodes.
--
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
