[HDFS-4413] Secondary namenode won't start if HDFS isn't the default file system

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1-win, 1.2.1
• Fix Version/s: 1.2.0
• Component/s: namenode
• Target Version/s: 1.2.0, 1-win
• Hadoop Flags: Reviewed
• Assignee: Mostafa Elhemali
• Reporter: Mostafa Elhemali
• Created: 16/Jan/13 23:55
• Updated: 15/Jul/13 00:10
• Resolved: 10/Apr/13 03:57

Description

If HDFS is not the default file system (fs.default.name is something other than hdfs://...), then secondary namenode throws early on in its initialization. This is a needless check as far as I can tell, and blocks scenarios where HDFS services are up but HDFS is not the default file system.