[ https://issues.apache.org/jira/browse/HDFS-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771368#comment-13771368 ]
Chuan Liu commented on HDFS-4320: --------------------------------- I created a new JIRA HDFS-5227 to track the issue in trunk. > Add a separate configuration for namenode rpc address instead of only using > fs.default.name > ------------------------------------------------------------------------------------------- > > Key: HDFS-4320 > URL: https://issues.apache.org/jira/browse/HDFS-4320 > Project: Hadoop HDFS > Issue Type: Improvement > Components: datanode, namenode > Affects Versions: 1.1.0, 3.0.0, 2.1.1-beta > Reporter: Mostafa Elhemali > Assignee: Mostafa Elhemali > Fix For: 1.2.0 > > Attachments: HDFS-4320.branch-1.2.patch, HDFS-4320.branch-1.3.patch, > HDFS-4320.patch, HDFS-4320.trunk.2.patch, HDFS-4320-trunk.3.patch, > HDFS-4320-trunk.4.patch, HDFS-4320.trunk.patch > > > 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. 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