hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haohui Mai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5122) WebHDFS should support logical service names in URIs
Date Wed, 11 Sep 2013 21:24:52 GMT

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

Haohui Mai commented on HDFS-5122:

Hi Alejandro,

I believe that this patch realizes your intuitions from 3~6, mostly reusing the current retry
logic of WebHDFS.

For (1), can you please elaborate your ideas on why introducing an additional redirector on
the server side? Right now the client will get a StandbyException and simply retry.

For (2), I appreciate if you could kindly give me a pointer to the actual method.

For (7), this patch forgets about the delegation token when the client connects to a different
name node. Based on my understanding it should be a simple approach to get things working.
I'm wondering whether WebHDFS needs a more sophisticated approach here. Can you elaborate
how the DFS client handle this case?
> WebHDFS should support logical service names in URIs
> ----------------------------------------------------
>                 Key: HDFS-5122
>                 URL: https://issues.apache.org/jira/browse/HDFS-5122
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: ha, webhdfs
>    Affects Versions: 2.1.0-beta
>            Reporter: Arpit Gupta
>            Assignee: Haohui Mai
>         Attachments: HDFS-5122.patch
> For example if the dfs.nameservices is set to arpit
> {code}
> hdfs dfs -ls webhdfs://arpit:50070/tmp
> or 
> hdfs dfs -ls webhdfs://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