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

Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2017/11/09 02:47:00 UTC

[jira] [Updated] (HBASE-17004) Refactor IntegrationTestManyRegions to use @ClassRule for timing out

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

Andrew Purtell updated HBASE-17004:
-----------------------------------
    Fix Version/s:     (was: 1.4.0)

> Refactor IntegrationTestManyRegions to use @ClassRule for timing out
> --------------------------------------------------------------------
>
>                 Key: HBASE-17004
>                 URL: https://issues.apache.org/jira/browse/HBASE-17004
>             Project: HBase
>          Issue Type: Improvement
>          Components: integration tests
>            Reporter: Appy
>            Assignee: Appy
>            Priority: Minor
>             Fix For: 2.0.0, 1.3.0, 1.2.5, 1.1.8
>
>         Attachments: HBASE-17004.master.001.patch, HBASE-17004.master.002.patch
>
>
> IntegrationTestManyRegions verifies that many regions get assigned within given time. To do so, it spawns a new thread and uses CountDownLatch.await() to timeout. Replacing this mechanism with junit @ClassRule to timeout the test.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)