[
https://issues.apache.org/jira/browse/PHOENIX-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261867#comment-17261867
]
Viraj Jasani commented on PHOENIX-6288:
---------------------------------------
Sure, definitely we can get more thoughts on perf improvement once we have at
least two consecutive QA results without issues in *initMiniCluster()*.
Recently, we have seen many 4.x PRs with +1 for unit tests, but I don't think I
have ever seen +1 for unit tests in master PRs (except for those with just xml
changes maybe).
{quote}The best solution would be figuring out a way to make the current
solution stable.
{quote}
Agree.
{quote}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.
{quote}
Sure [~stoty], let me raise a PR soon. Good to know how much more time entire
build takes with reuseForks=false.
> 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)
