Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 31 May 2012 18:35:23 +0000 (UTC)
From: "Aaron T. Myers (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <281773114.23066.1338489323265.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Created] (HDFS-3484) hdfs fsck doesn't work if NN HTTP
 address is set to 0.0.0.0 even if NN RPC address is configured
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Aaron T. Myers created HDFS-3484:
------------------------------------

             Summary: hdfs fsck doesn't work if NN HTTP address is set to 0.0.0.0 even if NN RPC address is configured
                 Key: HDFS-3484
                 URL: https://issues.apache.org/jira/browse/HDFS-3484
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: hdfs client
    Affects Versions: 2.0.0-alpha
            Reporter: Aaron T. Myers
            Assignee: Aaron T. Myers
            Priority: Minor


The default NN HTTP address is 0.0.0.0. Clients which need to connect to the HTTP address (e.g. fsck and fetchImage) need an address which is actually resolvable, however. If the configured NN HTTP address is set to 0.0.0.0, these clients should fall back on using the hostname configured for the RPC address, with the port configured for the HTTP address.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira