[jira] [Commented] (HBASE-7455) Increase timeouts in TestReplication and TestSplitLogWorker

["Jean-Daniel Cryans (JIRA)" <ji...@apache.org>]

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

Jean-Daniel Cryans commented on HBASE-7455:
-------------------------------------------

The problem with raising the timeouts that much is that currently some of the tests (testStartStop, testDisableEnable, testDisableInactivePeer, testAddAndRemoveClusters) always wait the full timeout because they check if something didn't happen. This makes TestReplication/TestReplicationWithCompression run at least 2 minutes longer than they need to be.
                
> 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
>            Assignee: 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