[
https://issues.apache.org/jira/browse/HDFS-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron T. Myers updated HDFS-2839:
---------------------------------
Description:
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.
was:
There might be two issues with having a nameservice id in fully qualified paths
of the files.
1) Some applications might be storing the fully qualified paths. They will have
hostnames from pre-ha installations, and they might break after the failover.
2) 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.
Summary: HA: Remove need for client configuration of nameservice ID
(was: Nameservice id in file uri could cause issues)
OK, that's fine. I've updated the JIRA summary and description to reflect this.
> 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
