[
https://issues.apache.org/jira/browse/PHOENIX-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samarth Jain updated PHOENIX-4110:
----------------------------------
Attachment: PHOENIX-4110_addendum_4.x-HBase-0.98.patch
For some reason, concurrently shutting down a mini cluster while another one is
coming up doesn't seem to work well for 4.x-HBase-0.98. Opting to use the
sameThreadExecutor for now.
> Shutdown mini cluster when number of tables grows beyond a threshold
> --------------------------------------------------------------------
>
> 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_addendum_4.x-HBase-0.98.patch,
> PHOENIX-4110.patch, PHOENIX-4110_v10.patch, PHOENIX-4110_v10.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, PHOENIX-4110_v7.patch, PHOENIX-4110_v8.patch,
> PHOENIX-4110_v9.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)
