hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yanbo Liang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-4212) NameNode can't differentiate between a never-created block and a block which is really missing
Date Thu, 29 Nov 2012 11:14:58 GMT

     [ https://issues.apache.org/jira/browse/HDFS-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yanbo Liang updated HDFS-4212:
------------------------------

    Attachment: hdfs-4212-junit-test.patch

I write a test case and run it against with the trunk code. I did not found the status you
mentioned above. Is this error can only happen in hadoop 1.* rather than 2.* or higher one?
or my test case is not correct to describe your condition? 
                
> 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
>         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