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] [Updated] (HDFS-3932) NameNode Web UI broken if the rpc-address is set to the wildcard
Date Thu, 20 Sep 2012 18:06:08 GMT

     [ https://issues.apache.org/jira/browse/HDFS-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Colin Patrick McCabe updated HDFS-3932:
---------------------------------------

    Attachment: HDFS-3932.007.patch

* Use {{NetUtils.getConnectAddress}}

* Update JavaDoc for {{NetUtils.getConnectAddress}}

Testing: I ran the unit test.  I also deployed this on a machine with a hostname that could
be looked up (did not only resolve to 127.0.0.1), and observed that the external IP address
got used to make URLs in the web UI.

(Just FYI, it still displays 0.0.0.0 in some places... but that is purely cosmetic I believe.
 It will be fixed with 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, 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