hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-1981) When namenode goes down while checkpointing and if is started again subsequent Checkpointing is always failing
Date Mon, 23 May 2011 11:14:47 GMT
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.23.0
         Environment: Linux
            Reporter: ramkrishna.s.vasudevan
             Fix For: 0.23.0


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

Mime
View raw message