hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joep Rottinghuis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5123) Hftp should support namenode logical service names in URI
Date Fri, 20 Sep 2013 20:22:54 GMT

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

Joep Rottinghuis commented on HDFS-5123:

[~andrew.wang] saw your comment in HDFS-5221.
Seems approach 1) is great, but not enough to solve ability to copy Hadoop 1.x cluster to
a Hadoop 2.x cluster. For that we need approach 2).
> Hftp should support namenode logical service names in URI
> ---------------------------------------------------------
>                 Key: HDFS-5123
>                 URL: https://issues.apache.org/jira/browse/HDFS-5123
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: ha
>    Affects Versions: 2.1.0-beta
>            Reporter: Arpit Gupta
> For example if the dfs.nameservices is set to arpit
> {code}
> hdfs dfs -ls hftp://arpit:50070/tmp
> or 
> hdfs dfs -ls hftp://arpit/tmp
> {code}
> does not work
> You have to provide the exact active namenode hostname. On an HA cluster using dfs client
one should not need to provide the active nn hostname

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message