[
https://issues.apache.org/jira/browse/PHOENIX-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261826#comment-17261826
]
Istvan Toth commented on PHOENIX-6288:
--------------------------------------
The intended operation is that we start a pool of 7 JVMs for each test
category, and for the Parallel* categories, we only initialize one minicluster,
and keep reusing the same JVM for each test (that is is assigned to the that
JVM).
As we don't want to go too large with the clusters, after a certain number of
test tables have been created, we shut down the minicluster in @AfterClass.
The @BeforeClass of the next test (on that JVM) will detect that there is no
cluster running, and start a new one.
Well, this is the intended operation, but obviously, this doesn't always work.
I do think that knowing the performance impact of running everything with
reuseForks=false would be great. Just link the PR here, so that we all can see
the Yetus results.
> Minicluster startup problems on Jenkins
> ---------------------------------------
>
> Key: PHOENIX-6288
> URL: https://issues.apache.org/jira/browse/PHOENIX-6288
> Project: Phoenix
> Issue Type: Bug
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Critical
> Fix For: 5.1.0, 4.16.0
>
>
> We are sporadically getting Test failures on Jenkins that are caused by the
> miniCluster startup timeouts.
> {noformat}
> Caused by: java.lang.RuntimeException: Master not active after 30000ms at
> org.apache.hadoop.hbase.util.JVMClusterUtil.waitForEvent(JVMClusterUtil.java:232)
>
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:188)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:430)
> at org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:259)
> ... 43 more
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
