[HDFS-4233] NN keeps serving even after no journals started while rolling edit

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.23.5
• Fix Version/s: 0.23.6
• Component/s: namenode
• Target Version/s: 0.23.6
• Hadoop Flags: Reviewed
• Assignee: Kihwal Lee
• Reporter: Kihwal Lee
• Created: 28/Nov/12 21:03
• Updated: 02/May/13 02:29
• Resolved: 30/Nov/12 06:02

Description

We've seen namenode keeps serving even after rollEditLog() failure. Instead of taking a corrective action or regard this condition as FATAL, it keeps on serving and modifying its file system state. No logs are written from this point, so if the namenode is restarted, there will be data loss.

Issue Links

• breaks: HDFS-4254 testAllEditsDirsFailOnFlush makes subsequent test cases fail (0.23.6 only)
• depends upon: HADOOP-9108 Add a method to clear terminateCalled to ExitUtil for test cases
• relates to: HADOOP-9137 Support connection limiting in IPC server