[
https://issues.apache.org/jira/browse/HDFS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565978#comment-13565978
]
Brandon Li commented on HDFS-4212:
----------------------------------
@Konstantin, never-created block is the block with the blockId assigned by
NameNode but never created on datanode. NameNode reports this block as missing,
and can't delete it from any DataNode. I mentioned this in HDFS-4212 and
HDFS-4280, but maybe I should have made it more obvious in the description.
This could happen when the client couldn't get the addBlock() response from
NameNode.
I am totally OK if you want to use HDFS-4452 to track this problem since it has
much clearer description.
> NameNode can't differentiate between a never-created block and a block which
> is really missing
> ----------------------------------------------------------------------------------------------
>
> Key: HDFS-4212
> URL: https://issues.apache.org/jira/browse/HDFS-4212
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 1.2.0, 3.0.0
> Reporter: Brandon Li
> Assignee: Brandon Li
> Attachments: hdfs-4212-junit-test.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
