hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3932) NameNode Web UI broken if the rpc-address is set to the wildcard
Date Thu, 20 Sep 2012 22:57:07 GMT

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

Daryn Sharp commented on HDFS-3932:
-----------------------------------

Yes, the javadoc is wrong.  If the given address is the wildcard address, it tries to use
the address of the first active interface.  If there are no active interfaces, it will use
the loopback address.
                
> 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
>
>
> 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