[
https://issues.apache.org/jira/browse/HDFS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565951#comment-13565951
]
Suresh Srinivas commented on HDFS-4212:
---------------------------------------
{quote}
If you knew the problem since November why didn't you report it correctly, it
would have saved me and others a lot of time...
How should I understand you were talking about getAdditionalBlock() and what in
the hell "a never-created block" means, if it is in fsimage.
{quote}
Relax :-)
We had reported the problem that we had found long back during HA testing. Few
week back we had discussed about the solution (thanks to [~sanjay.radia] for
suggesting this) of making getAdditionalBlock() truly idempotent and were
thinking of fixing it soon.
> 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
