Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 6 Feb 2013 01:14:11 +0000 (UTC)
From: "Andrew Wang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12630978.1360109828400.250554.1360113251206@arcas>
In-Reply-To: <JIRA.12630978.1360109828400@arcas>
References: <JIRA.12630978.1360109828400@arcas>
Subject: [jira] [Updated] (HDFS-4471) Namenode WebUI file browsing does not
 work with wildcard addresses configured
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Wang updated HDFS-4471:
------------------------------

    Attachment: hdfs-4471-1.patch

Patch attached. Tested via firing up a two node cluster (1 NN and 1 DN) with wildcard addresses configured. Checked the file browser (which worked), and visually the URL now has a proper IP address.
                
> 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