hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6336) Cannot download file via webhdfs when wildcard is enabled
Date Tue, 06 May 2014 20:40:16 GMT

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

Kihwal Lee commented on HDFS-6336:
----------------------------------

This is a config issue.  Are you setting {{fs.defaultFs}} to "0.0.0.0:8020"?  That will  causes
a lot of problems.
If you want namenode to bind to a wildcard address, try following:
{{fs.defaultFs}} = hdfs://real_nn_host_name_or_ip_addr:8020
{{dfs.namenode.rpc-bind-host}} = 0.0.0.0



> Cannot download file via webhdfs when wildcard is enabled
> ---------------------------------------------------------
>
>                 Key: HDFS-6336
>                 URL: https://issues.apache.org/jira/browse/HDFS-6336
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode, webhdfs
>    Affects Versions: 2.4.0
>            Reporter: Yongjun Zhang
>            Assignee: Yongjun Zhang
>         Attachments: HDFS-6336.001.patch, HDFS-6336.001.patch, HDFS-6336.001.patch
>
>
> With wildcard is enabled, issuing a webhdfs command like
> {code}
> http://yjztvm2.private:50070/webhdfs/v1/tmp?op=OPEN
> {code}
> would give
> {code}
> http://yjztvm3.private:50075/webhdfs/v1/tmp?op=OPEN&namenoderpcaddress=0.0.0.0:8020&offset=0
> {"RemoteException":{"exception":"ConnectException","javaClassName":"java.net.ConnectException","message":"Call
From yjztvm3.private/192.168.142.230 to 0.0.0.0:8020 failed on connection exception: java.net.ConnectException:
Connection refused; For more details see:  http://wiki.apache.org/hadoop/ConnectionRefused"}}
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message