Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 17 Dec 2012 22:10:13 +0000 (UTC)
From: "Mostafa Elhemali (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12624359.1355782165623.19339.1355782213397@arcas>
In-Reply-To: <JIRA.12624359.1355782165623@arcas>
References: <JIRA.12624359.1355782165623@arcas>
Subject: [jira] [Created] (HDFS-4320) NameNode tries to get its address by
 looking at fs.default.name instead of its own config keys
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Mostafa Elhemali created HDFS-4320:
--------------------------------------

             Summary: NameNode tries to get its address by looking at fs.default.name instead of its own config keys
                 Key: HDFS-4320
                 URL: https://issues.apache.org/jira/browse/HDFS-4320
             Project: Hadoop HDFS
          Issue Type: Bug
            Reporter: Mostafa Elhemali


When NameNode starts up, it tries to find out its address by looking at the fs.default.name configuration key instead of using its own keys (namely dfs.namenode.servicerpc-address). This breaks scenarios where we try to configure a Hadoop cluster that uses a different default file system than DFS, but still try to prop up namenode and datanode services as a secondary file system.

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