[HADOOP-2275] Erroneous detection of corrupted file when namenode fails to allocate any datanodes for newly allocated block

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.15.0
• Fix Version/s: 0.16.0
• Assignee: Dhruba Borthakur
• Reporter: Dhruba Borthakur
• Created: 26/Nov/07 08:01
• Updated: 08/Jul/09 16:42
• Resolved: 29/Nov/07 13:53

Description

It can so happen that the namenode allocated a block for a file and then fails to allocate any datanode for this block. The namenode delivers an exception to the client. The client retries. But the block remains associated with the file (until lease expiration). This causes all client retries to fail.

An fsck (before the lease expires) reports this block as a missing block.