hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3932) NameNode Web UI broken if the rpc-address is set to the wildcard
Date Fri, 21 Sep 2012 01:41:08 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460122#comment-13460122
] 

Colin Patrick McCabe commented on HDFS-3932:
--------------------------------------------

This latest patch replaces getNameNodeRpcAddressForHttpServer entirely with getConnectAddress.

testing: I ran this patch on a server with correct DNS setup, and observed that the nnaddr
was no longer 0.0.0.0 but instead a routable IP when looking at "Live Nodes"
                
> 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, 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

Mime
View raw message