hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "amith (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3585) Blocks are getting marked as corrupt when commitblocksyncronization(Since recovery called by another client) is success before BR send
Date Mon, 02 Jul 2012 10:46:22 GMT

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

amith commented on HDFS-3585:
-----------------------------

Here the scenario is 

1. Create 2 clients
2. write a file using the client 1
3. trigger a BR
4. trigger lease recovery from the client 2
5. let client 2 complete its recovery in DN and let commitBlockSync complete
6. Now allow the old BR to process which is triggered @ 3
7. The block is marked as corrupt in this scenario


                
> Blocks are getting marked as corrupt when commitblocksyncronization(Since recovery called
by another client) is success before BR send
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-3585
>                 URL: https://issues.apache.org/jira/browse/HDFS-3585
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 2.0.1-alpha, 3.0.0
>            Reporter: Brahma Reddy Battula
>
> Scenario:
> ===========
> Writing files without close
> renaming file
> deleting files with four DN's and replication factor=3

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message