[
https://issues.apache.org/jira/browse/HDFS-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460358#comment-13460358
]
Steve Loughran commented on HDFS-3932:
--------------------------------------
BTW, has anyone tested this on
# box w/ multiple addresses
# 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.
Networking is one area that has higher variance across installations than any
other -and a high variance in understanding, especially for people setting up
pseudo clusters. Hadoop needs to fail in a way that lets them know it's their
problem, not the Hadoop codebase.
> 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
