[
https://issues.apache.org/jira/browse/PHOENIX-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16149653#comment-16149653
]
James Taylor commented on PHOENIX-4110:
---------------------------------------
bq. restart the mini cluster in @Before and @After methods
I think this may be problematic. Another easy solution is to break up the test
into multiple ones. You can have an abstract base class with as many concrete
subclasses as you need (each with a subset of the tests).
> ParallelRunListener should monitor number of tables and not number of tests
> ---------------------------------------------------------------------------
>
> Key: PHOENIX-4110
> URL: https://issues.apache.org/jira/browse/PHOENIX-4110
> Project: Phoenix
> Issue Type: Bug
> Reporter: Samarth Jain
> Assignee: Samarth Jain
> Attachments: PHOENIX-4110.patch,
> PHOENIX-4110_V2_4.x-HBase-0.98.patch, PHOENIX-4110_v3_4.x-HBase-0.98.patch,
> PHOENIX-4110_v3.patch, PHOENIX-4110_v4.patch, PHOENIX-4110_v5.patch,
> PHOENIX-4110_v6.patch
>
>
> ParallelRunListener today monitors the number of tests that have been run to
> determine when mini cluster should be shut down. This helps prevent our test
> JVM forks running in OOM. A better heuristic would be to instead check the
> number of tables that were created by tests. This way when a particular test
> class has created lots of tables, we can shut down the mini cluster sooner.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
