[
https://issues.apache.org/jira/browse/HDFS-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202821#comment-13202821
]
Todd Lipcon commented on HDFS-2839:
-----------------------------------
One possibility we'd discussed last year is to use DNS "SRV" records, and have
a different ConfiguredClientProxyProvider implementation that grabs the list of
NNs from the SRV instead of the local conf.
Of course the question then is how the unconfigured client knows to even look
for the SRV record -- unless this becomes a default fallback in response to a
"host not found" -- ie if hdfs://foo.example.com is used, but there is no A or
CNAME record, then assume HA and fall back to SRV?
> HA: Remove need for client configuration of nameservice ID
> ----------------------------------------------------------
>
> Key: HDFS-2839
> URL: https://issues.apache.org/jira/browse/HDFS-2839
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, hdfs client, name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
>
> The fully qualified path from an ha cluster, won't be usable from a different
> cluster that doesn't know about that particular namespace id.
--
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
