[ https://issues.apache.org/jira/browse/HDFS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071697#comment-13071697 ]
Uma Maheswara Rao G commented on HDFS-1981: ------------------------------------------- *Reason for above failures:* This patch is based on 0.22 branch. So, HDFS-1981_0.22.patch can not compile on trunk directly. > When namenode goes down while checkpointing and if is started again > subsequent Checkpointing is always failing > -------------------------------------------------------------------------------------------------------------- > > Key: HDFS-1981 > URL: https://issues.apache.org/jira/browse/HDFS-1981 > Project: Hadoop HDFS > Issue Type: Bug > Components: name-node > Affects Versions: 0.22.0 > Environment: Linux > Reporter: ramkrishna.s.vasudevan > Assignee: Uma Maheswara Rao G > Priority: Blocker > Fix For: 0.22.0 > > Attachments: HDFS-1981-1.patch, HDFS-1981-2.patch, HDFS-1981.patch, > HDFS-1981_0.22.patch, HDFS-1981_0.23.patch > > > 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira