[
https://issues.apache.org/jira/browse/HDFS-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460880#comment-13460880
]
Colin Patrick McCabe commented on HDFS-3932:
--------------------------------------------
With respect to Steve's scenario #2 ("box with totally broken networking"):
bq. ... a box with totally broken networking that returns null instead of a
hostname/IP addr. One of mine with a buggy resolv.conf had this. Such a box is
beyond hope -the goal should just be to bail out with a message saying "your
network is broken", instead of a stack trace.
I guess I should mention that {{NetUtils#getConnectAddress}} will return
{{127.0.0.1}} if no local hostnames can be resolved. I think that's pretty
much as best as we can handle it, although I'm open for other ideas.
> 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
> Fix For: 2.0.3-alpha
>
> Attachments: HDFS-3932.001.patch, HDFS-3932.002.patch,
> HDFS-3932.003.patch, HDFS-3932.005.patch, HDFS-3932.006.patch,
> HDFS-3932.007.patch, HDFS-3932.008.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
