[HDFS-3605] Block mistakenly marked corrupt during edit log catchup phase of failover

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0-alpha
• Fix Version/s: 2.0.2-alpha
• Component/s: ha, namenode
• Hadoop Flags: Reviewed
• Assignee: Todd Lipcon
• Reporter: Brahma Reddy Battula
• Created: 06/Jul/12 18:39
• Updated: 04/Sep/14 00:59
• Resolved: 18/Jul/12 23:43

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.