hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3770) TestFileConcurrentReader#testUnfinishedBlockCRCErrorTransferToAppend failed
Date Mon, 13 Aug 2012 18:56:38 GMT

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

Hudson commented on HDFS-3770:

Integrated in Hadoop-Hdfs-trunk-Commit #2637 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2637/])
    Revert HDFS-3719. See discussion there and HDFS-3770 for more info. (Revision 1372544)

     Result = SUCCESS
atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1372544
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestFileConcurrentReader.java

> TestFileConcurrentReader#testUnfinishedBlockCRCErrorTransferToAppend failed
> ---------------------------------------------------------------------------
>                 Key: HDFS-3770
>                 URL: https://issues.apache.org/jira/browse/HDFS-3770
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 3.0.0
>            Reporter: Eli Collins
> TestFileConcurrentReader#testUnfinishedBlockCRCErrorTransferToAppend failed on [a recent
job|https://builds.apache.org/job/PreCommit-HDFS-Build/2959]. Looks like a race in the test.
The failure is due to a ChecksumException but that's likely due to the DFSOutputstream getting
interrupted on close. Looking at the relevant code, waitForAckedSeqno is getting an InterruptedException
waiting on dataQueue, looks like there are uses of interrupt where we're not first notifying
dataQueue, or waiting for the notifications to be delivered.

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


View raw message