[HDFS-4212] NameNode can't differentiate between a never-created block and a block which is really missing

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.2.0, 3.0.0-alpha1
• Component/s: namenode
• Assignee: Brandon Li
• Reporter: Brandon Li
• Created: 20/Nov/12 07:23
• Updated: 12/May/16 18:15
• Resolved: 31/Jan/13 00:07

Description

In one test case, NameNode allocated a block and then was killed before the client got the addBlock response.

After NameNode restarted, the block which was never created was considered as a missing block and FSCK would report the file is corrupted.

The problem seems to be that, NameNode can't differentiate between a never-created block and a block which is really missing.

Issue Links

• is duplicated by: HDFS-4452 getAdditionalBlock() can create multiple blocks if the client times out and retries.
• is related to: HDFS-4208 NameNode could be stuck in SafeMode due to never-created blocks