Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-1981

When namenode goes down while checkpointing and if is started again subsequent Checkpointing is always failing

    Details

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

      Linux

    • Hadoop Flags:
      Reviewed

      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.

        Attachments

        1. HDFS-1981.patch
          5 kB
          ramkrishna.s.vasudevan
        2. HDFS-1981-1.patch
          5 kB
          ramkrishna.s.vasudevan
        3. HDFS-1981-2.patch
          4 kB
          ramkrishna.s.vasudevan
        4. HDFS-1981_0.23.patch
          4 kB
          Uma Maheswara Rao G
        5. HDFS-1981_0.22.patch
          4 kB
          Uma Maheswara Rao G

          Issue Links

            Activity

              People

              • Assignee:
                umamaheswararao Uma Maheswara Rao G
                Reporter:
                ram_krish ramkrishna.s.vasudevan
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: