You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Mostafa Elhemali (JIRA)" <ji...@apache.org> on 2012/12/17 23:10:13 UTC

[jira] [Created] (HDFS-4320) NameNode tries to get its address by looking at fs.default.name instead of its own config keys

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