[HADOOP-4692] Namenode in infinite loop for replicating/deleting corrupted block

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.18.0
• Fix Version/s: 0.20.0
• Assignee: Hairong Kuang
• Reporter: Hairong Kuang
• Created: 20/Nov/08 00:24
• Updated: 02/May/13 02:29
• Resolved: 19/Feb/09 21:58

Description

Our cluster has an under-replicated block with only one replica, assuming its block id is B. NameNode log shows that NameNode is in an infinite loop replicating/deleting the block.

INFO org.apache.hadoop.dfs.StateChange: BLOCK* ask DN1 to replicate blk_B to datanode(s) DN2, DN3
WARN org.apache.hadoop.fs.FSNamesystem: Inconsistent size for block blk_B reported from DN2 current size is 134217728 reported size is 134205440
WARN org.apache.hadoop.fs.FSNamesystem: Deleting block blk_B from DN2
INFO org.apache.hadoop.dfs.StateChange: DIR* NameSystem.invalidateBlock: blk_B on DN2
INFO org.apache.hadoop.dfs.StateChange: BLOCK* NameSystem.delete: blk_B is added to invalidSet of DN2
INFO org.apache.hadoop.dfs.StateChange: BLOCK* NameSystem.addStoredBlock: blockMap updated: DN2 is added to blk_B size 134217728
WARN org.apache.hadoop.fs.FSNamesystem: Inconsistent size for block blk_-B reported from DN3 current size is 134217728 reported size is 134205440
WARN org.apache.hadoop.fs.FSNamesystem: Deleting block blk_B from DN3
INFO org.apache.hadoop.dfs.StateChange: DIR* NameSystem.invalidateBlock: blk_B on DN3
INFO org.apache.hadoop.dfs.StateChange: BLOCK* NameSystem.delete: blk_B is added to invalidSet of DN3
INFO org.apache.hadoop.dfs.StateChange: BLOCK* NameSystem.addStoredBlock: blockMap updated: DN3 is added to blk_B size 134217728
INFO org.apache.hadoop.dfs.StateChange: BLOCK* ask DN1 to replicate blk_B to datanode(s) DN4, DN5
...

Issue Links

• depends upon: HDFS-221 Trigger block scans for datanode
• is blocked by: HDFS-168 Block report processing should compare gneration stamp