[
https://issues.apache.org/jira/browse/HDFS-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459740#comment-13459740
]
Eli Collins commented on HDFS-3932:
-----------------------------------
NetUtils#getConnectAddress claims it returns the loopback when the wildcard is
passed, but that's not what we want here. We only want the loopback on dev
machines when the hostname doesn't map to a non-loopback IP. However perhaps
the javadoc is wrong because looking at the code I don't think it always
returns the loopback when the wildcard is passed, so I think you're right.
Colin, want to confirm and update the patch?
> NameNode Web UI broken if the rpc-address is set to the wildcard
> -------------------------------------------------------------------
>
> Key: HDFS-3932
> URL: https://issues.apache.org/jira/browse/HDFS-3932
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 1.0.3, 2.0.0-alpha
> Reporter: Eli Collins
> Assignee: Eli Collins
> Attachments: HDFS-3932.001.patch, HDFS-3932.002.patch,
> HDFS-3932.003.patch, HDFS-3932.005.patch, HDFS-3932.006.patch
>
>
> If {{dfs.namenode.rpc-address}} is set to the wildcard some of links in the
> dfsnodelist.jsp and browseDirectory.jsp pages are broken because the nnaddr
> field is passed verbatim (eg nnaddr=0.0.0.0:8021).
--
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
