You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2015/12/18 08:27:46 UTC

[jira] [Updated] (HBASE-13617) TestReplicaWithCluster.testChangeTable timeout

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

Sean Busbey updated HBASE-13617:
--------------------------------
    Component/s: test

> TestReplicaWithCluster.testChangeTable timeout
> ----------------------------------------------
>
>                 Key: HBASE-13617
>                 URL: https://issues.apache.org/jira/browse/HBASE-13617
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 2.0.0, 1.1.0, 1.2.0
>            Reporter: Stephen Yuan Jiang
>            Assignee: Stephen Yuan Jiang
>             Fix For: 2.0.0, 1.2.0, 1.1.1
>
>         Attachments: HBASE-13617.patch
>
>
> In our internal test TestReplicaWithCluster.testChangeTable got a timeout.  
> HBASE-12170 bumped TestReplicaWithCluster.testReplicaAndReplication timeout from 2 minutes to 5 minutes, but leaves other tests in the same package unchanged.
> When I run the test in my fast Mac, the run time of TestReplicaWithCluster.testChangeTable (~16 seconds) is about half of TestReplicaWithCluster.testReplicaAndReplication (~31 seconds).  
> We should increase the timeout in TestReplicaWithCluster.testChangeTable to avoid test failure in slow environment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)