Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6939EE743 for ; Wed, 6 Feb 2013 19:27:15 +0000 (UTC) Received: (qmail 73483 invoked by uid 500); 6 Feb 2013 19:27:15 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 73455 invoked by uid 500); 6 Feb 2013 19:27:15 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 73446 invoked by uid 99); 6 Feb 2013 19:27:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Feb 2013 19:27:15 +0000 Date: Wed, 6 Feb 2013 19:27:15 +0000 (UTC) From: "Daryn Sharp (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572708#comment-13572708 ] Daryn Sharp commented on HDFS-4471: ----------------------------------- It'd might be better to use the host/port in the request context. > 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