hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4212) NameNode can't differentiate between a never-created block and a block which is really missing
Date Wed, 30 Jan 2013 19:31:14 GMT

    [ https://issues.apache.org/jira/browse/HDFS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566815#comment-13566815
] 

Konstantin Shvachko commented on HDFS-4212:
-------------------------------------------

Brandon I checked both issues. They seem to be dealing with the consequences of the problem.
>From what I hear Sanjay's assessment is right.
The closest by description issue I found so far is HDFS-3031.

Let's use HDFS-4452 since it addresses the problem directly.
I want to make a patch ready this week. LMK if you can work on it now.

To accelerate we can split the work. I have getAdditionalBlock() impl almost ready. But there
is much more: RPC, DFSClient, and tests. I can get you a diff of FSNamesystem. You can merge
it and submit the patch under HDFS-4452.
                
> 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

Mime
View raw message