[
https://issues.apache.org/jira/browse/PHOENIX-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17262693#comment-17262693
]
Istvan Toth commented on PHOENIX-6288:
--------------------------------------
Thanks.
My current understanding: It is not possible (at least with our setup) to start
a minicluster and stop a minicluster concurrently on the same JVM reliably,
even when we have everything synchronized, and we are guaranteed to start the
new cluster after we start the shutdown of the old one.
I can think of three possible solutions now:
* reuseForks=false - this is guaranteed to work, but adds ~16% to the test
execution time (as you've just shown)
* clean up HBase tables instead of restarting: - seems to work, not benchmarked
yet
* shutdown minicluster in the foreground: - not tested yet
> 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)
