[HDFS-1981] When namenode goes down while checkpointing and if is started again subsequent Checkpointing is always failing

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.22.0
• Fix Version/s: 0.22.0
• Component/s: namenode

Environment

Linux

• Hadoop Flags: Reviewed
• Assignee: Uma Maheswara Rao G
• Reporter: ramkrishna.s.vasudevan
• Created: 23/May/11 11:13
• Updated: 12/Dec/11 06:19
• Resolved: 27/Jul/11 23:35

Description

This scenario is applicable in NN and BNN case.

When the namenode goes down after creating the edits.new, on subsequent restart the divertFileStreams will not happen to edits.new as the edits.new file is already present and the size is zero.

so on trying to saveCheckPoint an exception occurs
2011-05-23 16:38:57,476 WARN org.mortbay.log: /getimage: java.io.IOException: GetImage failed. java.io.IOException: Namenode has an edit log with timestamp of 2011-05-23 16:38:56 but new checkpoint was created using editlog with timestamp 2011-05-23 16:37:30. Checkpoint Aborted.

This is a bug or is that the behaviour.

Issue Links

• relates to: HADOOP-5314 needToSave incorrectly calculated in loadFSImage()