[
https://issues.apache.org/jira/browse/HDFS-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458269#comment-13458269
]
Colin Patrick McCabe commented on HDFS-3932:
--------------------------------------------
This is a simple patch which just uses the first available local hostname in
lieu of 0.0.0.0.
I tried the RPC-based approach, but it didn't quite work out, because the
{{NameNodeHttpServer}} needs to be initialized before the RPC stuff is quite
prepared.
The weakness of this approach is that it doesn't distinguish between external
and internal hostnames. However, this should not be a problem in most
scenarios. I think the full solution, which we should do later, is the
refactoring Eli proposed in HDFS-3946.
> 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
>
>
> 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
