[HDFS-140] When a file is deleted, its blocks remain in the blocksmap till the next block report from Datanode

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 0.20.1
• Assignee: Uma Maheswara Rao G
• Reporter: Dhruba Borthakur
• Created: 10/Aug/07 07:23
• Updated: 29/May/12 18:42
• Resolved: 02/Mar/12 14:02

Description

When a file is deleted, the namenode sends out block deletions messages to the appropriate datanodes. However, the namenode does not delete these blocks from the blocksmap. Instead, the processing of the next block report from the datanode causes these blocks to get removed from the blocksmap.

If we desire to make block report processing less frequent, this issue needs to be addressed. Also, this introduces indeterministic behaviout to a a few unit tests. Another factor to consider is to ensure that duplicate block detection is not compromised.

Issue Links

• is duplicated by: HDFS-1924 Block information displayed in UI is incorrect
• is duplicated by: HDFS-1230 BlocksMap.blockinfo is not getting cleared immediately after deleting a block.This will be cleared only after block report comes from the datanode.Why we need to maintain the blockinfo till that time.
• is related to: HDFS-37 An invalidated block should be removed from the blockMap