hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4471) Namenode WebUI file browsing does not work with wildcard addresses configured
Date Wed, 06 Feb 2013 20:03:12 GMT

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

Andrew Wang commented on HDFS-4471:
-----------------------------------

Hey Daryn, thanks for looking this over. I'm not that familiar with JSP, but it looks like
the NN is being pulled out of the {{context}} parameter, which I then use to get the address
and port:

{code}
    final NameNode nn = NameNodeHttpServer.getNameNodeFromContext(context);
<snip>
    InetSocketAddress connectAddr =
        NetUtils.getConnectAddress(nn.getNameNodeAddress());
    String addr = connectAddr.getAddress().getHostAddress()
        + ":" + connectAddr.getPort();
{code}

Is this the request context you were talking about?
                
> Namenode WebUI file browsing does not work with wildcard addresses configured
> -----------------------------------------------------------------------------
>
>                 Key: HDFS-4471
>                 URL: https://issues.apache.org/jira/browse/HDFS-4471
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 3.0.0
>            Reporter: Andrew Wang
>            Assignee: Andrew Wang
>         Attachments: hdfs-4471-1.patch
>
>
> The namenode web UI currently passes around the NN's configured RPC address in the URL.
One of the places this is used is for file browsing; the NN redirects to a random DN, and
the DN then uses the NN address from the URL to contact the NN. However, this fails when the
NN RPC address is configured to be the wildcard (0.0.0.0).
> The fix is the same as in HDFS-3932: pass the configured address through {{NetUtils#getConnectAddress}}
first.

--
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