Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 2 Jul 2012 13:13:22 +0000 (UTC)
From: "amith (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <729373909.356.1341234802707.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1931344927.77742.1341219225294.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HDFS-3585) Blocks are getting marked as corrupt
 when commitblocksyncronization(Since recovery called by another client) is
 success before BR send
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

In the mentioned scenario 
consider we a have block of GS 1002 and its reported to NN
Now DN has completed the recovery which should have bumped GS to 1003 and commitBlockSync successfully executed
Next the old block report is processed then there is a mismatch in the GS and reported ...!

SO the block is marked as corrupt  :(


> 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