Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 14 Apr 2011 22:18:05 +0000 (UTC)
From: "Matt Foley (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <151237501.59057.1302819485966.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1146430071.35474.1302024485808.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HDFS-1806) TestBlockReport.blockReport_08() and
 _09() are timing-dependent and likely to fail on fast servers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Matt Foley updated HDFS-1806:
-----------------------------

    Fix Version/s: 0.22.0
           Status: Patch Available  (was: Open)

> TestBlockReport.blockReport_08() and _09() are timing-dependent and likely to fail on fast servers
> --------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-1806
>                 URL: https://issues.apache.org/jira/browse/HDFS-1806
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node, name-node
>    Affects Versions: 0.22.0
>            Reporter: Matt Foley
>            Assignee: Matt Foley
>             Fix For: 0.22.0
>
>         Attachments: TestBlockReport.java.patch, blockReport_08_failure_log.html
>
>
> Method waitForTempReplica() polls every 100ms during block replication, attempting to "catch" a datanode in the state of having a TEMPORARY replica.  But examination of a current Hudson test failure log shows that the replica goes from "start" to "TEMPORARY" to "FINALIZED" in only 50ms, so of course the poll usually misses it.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira