hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2839) Nameservice id in file uri could cause issues
Date Wed, 25 Jan 2012 03:40:40 GMT

    [ https://issues.apache.org/jira/browse/HDFS-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192842#comment-13192842

Todd Lipcon commented on HDFS-2839:

For #1 above, you could configure the "logical URI" of the HA-ified cluster to match exactly
the hostname of the non-HA cluster.

For #2, I don't see any way around it -- you need some way of finding the hosts... unless
you are proposing a VIP based client failover approach here?
> 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
>    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
> 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


View raw message