[
https://issues.apache.org/jira/browse/HDFS-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458979#comment-13458979
]
Colin Patrick McCabe commented on HDFS-3932:
--------------------------------------------
bq. The test should also check for the loopback IP for sanity
Actually, I don't think that's possible with this approach. Some people
configure their computer to have a hostname simply by adding an entry like this
to {{/etc/hosts}}:
{code}
127.0.0.1 keter localhost
{code}
If there is no DNS server configured with a non-loopback address, then
{{/etc/hosts}} really is the only authority, and {{127.0.0.1}} really is the
only IP address bound to that hostname. I think a lot of developer boxes are
set up this way.
On the other hand, if there is a real DNS setup, there should be some way of
iterating through the IP addresses associated with our hostname. I'll see if I
can find some way of ensuring we use the non-loopback IP if it's available.
> 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
>
>
> 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
