Hadoop HDFS
  1. Hadoop HDFS
  2. HDFS-3605

Block mistakenly marked corrupt during edit log catchup phase of failover

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0-alpha
    • Fix Version/s: 2.0.2-alpha
    • Component/s: ha, namenode
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      Open file for append
      Write data and sync.
      After next log roll and editlog tailing in standbyNN close the append stream.
      Call append multiple times on the same file, before next editlog roll.
      Now abruptly kill the current active namenode.

      Here block is missed..

      this may be because of All latest blocks were queued in StandBy Namenode.
      During failover, first OP_CLOSE was processing the pending queue and adding the block to corrupted block.

      1. HDFS-3605.patch
        12 kB
        Uma Maheswara Rao G
      2. hdfs-3605.txt
        10 kB
        Todd Lipcon
      3. hdfs-3605.txt
        11 kB
        Todd Lipcon
      4. hdfs-3605.txt
        11 kB
        Todd Lipcon
      5. TestAppendBlockMiss.java
        4 kB
        Brahma Reddy Battula

        Activity

        Brahma Reddy Battula created issue -
        Brahma Reddy Battula made changes -
        Field Original Value New Value
        Description Open file for append
        Write data and sync.
        After next log roll and editlog tailing in standbyNN close the append stream.
        Call append multiple times on the same file, before next editlog roll.
        Now abruptly kill the current active namenode.

        Here block this block missed..

        this may be because of All latest blocks were queued in StandBy Namenode.
        During failover, first OP_CLOSE was processing the pending queue and adding the block to corrupted block.
        Open file for append
        Write data and sync.
        After next log roll and editlog tailing in standbyNN close the append stream.
        Call append multiple times on the same file, before next editlog roll.
        Now abruptly kill the current active namenode.

        Here block is missed..

        this may be because of All latest blocks were queued in StandBy Namenode.
        During failover, first OP_CLOSE was processing the pending queue and adding the block to corrupted block.
        Aaron T. Myers made changes -
        Summary Missing Block in following sceanrio. Missing Block in following scenario
        Brahma Reddy Battula made changes -
        Attachment TestAppendBlockMiss.java [ 12535784 ]
        Todd Lipcon made changes -
        Assignee Todd Lipcon [ tlipcon ]
        Suresh Srinivas made changes -
        Component/s ha [ 12316609 ]
        Todd Lipcon made changes -
        Summary Missing Block in following scenario Block mistakenly marked corrupt during edit log catchup phase of failover
        Uma Maheswara Rao G made changes -
        Attachment HDFS-3605.patch [ 12536372 ]
        Todd Lipcon made changes -
        Attachment hdfs-3605.txt [ 12536481 ]
        Todd Lipcon made changes -
        Status Open [ 1 ] Patch Available [ 10002 ]
        Todd Lipcon made changes -
        Attachment hdfs-3605.txt [ 12536725 ]
        Todd Lipcon made changes -
        Attachment hdfs-3605.txt [ 12536961 ]
        Todd Lipcon made changes -
        Status Patch Available [ 10002 ] Resolved [ 5 ]
        Hadoop Flags Reviewed [ 10343 ]
        Fix Version/s 2.1.0-alpha [ 12321440 ]
        Fix Version/s 3.0.0 [ 12320356 ]
        Resolution Fixed [ 1 ]
        Arun C Murthy made changes -
        Affects Version/s 2.1.0-alpha [ 12321440 ]
        Fix Version/s 2.0.2-alpha [ 12322472 ]
        Fix Version/s 2.1.0-alpha [ 12321440 ]
        Arun C Murthy made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Allen Wittenauer made changes -
        Fix Version/s 3.0.0 [ 12320356 ]

          People

          • Assignee:
            Todd Lipcon
            Reporter:
            Brahma Reddy Battula
          • Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development