[
https://issues.apache.org/jira/browse/HDFS-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13991312#comment-13991312
]
Yongjun Zhang commented on HDFS-6336:
-------------------------------------
Thank you all for the review and comments!
I guess I mistook Haohui's point a bit earlier. I tested HA/NonHA for this jira
issue, but not failover, which issue is handled by HDFS-6329 as Daryn pointed
out.
My {code}fs.defaultFs{code} was set to hdfs://real_nn_host_name:8020 as you
suggested, however, dfs.namenode.rpc-address was set to 0.0.0.0:8020 and I
don't see dfs.namenode.rpc-bind-host was set, . I tried to set
{code}rpc-address{code} to nn_host_name:8020, and {code}rpc-bind-host{code} to
0.0.0.0, and the problem is gone. So this is a config issue. Thanks for
pointing it out!
I will do some more testing.
> 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)
