Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 16 Mar 2012 17:41:41 +0000 (UTC)
From: "Todd Lipcon (Resolved) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <110710438.25527.1331919701886.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (HDFS-1197) Blocks are considered "complete"
 prematurely after commitBlockSynchronization or DN restart
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Todd Lipcon resolved HDFS-1197.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.20.205.0
         Assignee: Todd Lipcon

This was committed to branch-20 a long while back
                
> Blocks are considered "complete" prematurely after commitBlockSynchronization or DN restart
> -------------------------------------------------------------------------------------------
>
>                 Key: HDFS-1197
>                 URL: https://issues.apache.org/jira/browse/HDFS-1197
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node, hdfs client, name-node
>    Affects Versions: 0.20-append
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.20-append, 0.20.205.0
>
>         Attachments: HDFS-1197-20s.2.patch, HDFS-1197-20s.3.patch, HDFS-1197-without-addStoredBlock-change.1.patch, hdfs-1197-test-changes.txt, hdfs-1197.txt, testTC2-failure.txt
>
>
> I saw this failure once on my internal Hudson job that runs the append tests 48 times a day:
> junit.framework.AssertionFailedError: expected:<114688> but was:<98304>
> 	at org.apache.hadoop.hdfs.AppendTestUtil.check(AppendTestUtil.java:112)
> 	at org.apache.hadoop.hdfs.TestFileAppend3.testTC2(TestFileAppend3.java:116)

--
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