[
https://issues.apache.org/jira/browse/HDFS-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yongjun Zhang updated HDFS-6336:
--------------------------------
Status: Patch Available (was: Open)
This webhdfs issue is similar to the namenode web UI problem reported in
https://issues.apache.org/jira/browse/HDFS-4471 (which is fixed by
[~andrew.wang]). I made a similar fix here.
I attempted to create a unit test case by enabling wildcard address, but was
not successful. I did the test on a cluster of 4 nodes before and after the
fix, to see the fix resolve the problem.
Thanks Andrew for some consultation.
> 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
>
>
> 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)
