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) 0.20: TestFileAppend3.testTC2 failure
Date Thu, 10 Jun 2010 17:24:13 GMT

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

Todd Lipcon commented on HDFS-1197:
-----------------------------------

The sequence in this test was:
- Client opens existing block for append
- Client appends 16KB, closes pipeline
- Client calls completeFile() which finalizes the inode
- DN blockReceived calls arrive

I don't think we properly handle the case in checkFileProgress to see if we actually seen
finalized replicas of the newest generation stamp.

I'll work on a test case that delays the blockReceived calls

> 0.20: TestFileAppend3.testTC2 failure
> -------------------------------------
>
>                 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
>         Attachments: 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message