[jira] [Resolved] (PHOENIX-960) Don't spin mini cluster up and down between tests

["James Taylor (JIRA)" <ji...@apache.org>]

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

James Taylor resolved PHOENIX-960.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.2
                   4.2

This was fixed by [~samarth.jain@gmail.com] - thanks for the contributions. We spin up and down as few mini-clusters as we can now: one for client manage time tests, one for hbase managed time tests, and one for each test that needs it's own mini-cluster. This is controlled by an @Category annotation on the test class.

> Don't spin mini cluster up and down between tests
> -------------------------------------------------
>
>                 Key: PHOENIX-960
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-960
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: James Taylor
>            Assignee: Samarth Jain
>             Fix For: 4.2, 3.2
>
>
> The main reason for the slowness is the time it takes to spin up and tear down a mini cluster for each test suite. We do this to guarantee that there's no left over state from previous tests.
> A few things we can do to improve things:
> * consolidate test suites where it makes sense, if there are just a few strangler tests that can put combined with other test suites.
> * spin up  a single mini cluster and before a test suite runs, disable and drop any hbase tables that exist.



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