[HADOOP-1135] A block report processing may incorrectly cause the namenode to delete blocks

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.12.2
• Assignee: Dhruba Borthakur
• Reporter: Dhruba Borthakur
• Created: 20/Mar/07 16:50
• Updated: 08/Jul/09 16:42
• Resolved: 22/Mar/07 08:16

Description

When a block report arrives at the namenode, the namenode goes through all the blocks on that datanode. If a block is not valid it is marked for deletion. The blocks-to-be-deleted are sent to the datanode as a response to the next heartbeat RPC. The namenode sends only 100 blocks-to-be-deleted at a time. This was introduced as part of hadoop-994. The bug is that if the number of blocks-to-be-deleted exceeds 100, then that namenode marks all the remaining blocks in the block report for deletion.