hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7455) Increase timeouts in TestReplication and TestSplitLogWorker
Date Sat, 29 Dec 2012 11:54:15 GMT

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

Hudson commented on HBASE-7455:

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #318 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/318/])
    HBASE-7455 Increase timeouts in TestReplication and TestSplitLogWorker (Revision 1426710)

     Result = FAILURE
larsh : 
Files : 
* /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplication.java

> Increase timeouts in TestReplication and TestSplitLogWorker
> -----------------------------------------------------------
>                 Key: HBASE-7455
>                 URL: https://issues.apache.org/jira/browse/HBASE-7455
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>             Fix For: 0.96.0, 0.94.4
>         Attachments: 7455-0.94.txt, 7455-0.96.txt
> When I measure the times in TestReplication.queueFailover, it takes about 15s on my (reasonably
fast) Laptop.
> The timeout in queueFailover currently is 1500*2*15 = 45000ms.
> For setup before each test (which truncates the table and waits for the changes to replicate)
it is 1500*15 = 22500ms.
> Interestingly I see queueFailover failures where the wait time is measured as 64260ms
and some at 72316ms.
> Since these numbers are not even close to 45000ms, the machine or JVM must have been
stuck for 15 or almost 30s (otherwise we'd get a timeout and the total time spent should be
close to the timeout).
> So I would suggest that we increase the timeouts further.
> We could set SLEEP_TIME to 2000 and retries to 20. Would lead to 2000*2*20 = 80000ms.
> Any objections?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message