[
https://issues.apache.org/jira/browse/HDFS-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202172#comment-13202172
]
Aaron T. Myers commented on HDFS-2839:
--------------------------------------
bq. But #2 is still open and needs discussion. I think it is an important issue
because some applications do store the file paths. I agree it is not an highest
priority thing right now, but I would recommend keeping the jira open so that
it stays in the radar.
Isn't this identical to if a federated cluster is running, but some remote
client on another cluster doesn't have viewfs configured appropriately? It
seems that in any system where there's a client doing some resolution using a
logical URI, that this necessitates some client-side configuration. I don't see
any way around it.
> Nameservice id in file uri could cause issues
> ---------------------------------------------
>
> 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
>
> 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.
--
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
