[
https://issues.apache.org/jira/browse/PHOENIX-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261102#comment-17261102
]
Istvan Toth commented on PHOENIX-6288:
--------------------------------------
Does HBase reuse the miniCluster instances between tests the same way as
Phoenix does ?
My first thought is that having the same lifecycle for HbaseTestingUtility and
MiniCluster is a good thing (the current solution), as HTU holds references to
the clusters that it creates.
In fact, looking at this code again,BaseTest.tearDownMiniClusterAsync(int)
looks fishy.
We are using an HbaseTestingUtility instance to do the actual shutdown that
doesn't even know about the clusters that were created.
Let me do a PR to fix that, and add some belts and suspenders synchronization
around HbaseTestingUtility.
> 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)
