hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-1197) Blocks are considered "complete" prematurely after commitBlockSynchronization or DN restart
Date Wed, 07 Sep 2011 17:39:14 GMT

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

Todd Lipcon commented on HDFS-1197:

That seems to make sense. But given this patch has been in production for a year so in lots
of clusters, I'm more comfortable committing the full fix. Otherwise, would have to take a
lot of hours to think through the possibilities and edge cases again :)

> 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
>             Fix For: 0.20-append
>         Attachments: 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message