[ https://issues.apache.org/jira/browse/HDFS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565925#comment-13565925 ]
Konstantin Shvachko commented on HDFS-4212: ------------------------------------------- > Actually it is a problem related to HDFS-4452. Which problem? The original description of NN crashing before replying to the client is not a problem and not related to HDFS-4452. The problem in comment 2 here is exactly the problem I am talking, but posted after HDFS-4452 was created. 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. > 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