[
https://issues.apache.org/jira/browse/PHOENIX-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17262122#comment-17262122
]
Istvan Toth edited comment on PHOENIX-6288 at 1/10/21, 8:58 AM:
----------------------------------------------------------------
This is great, [~vjasani]
The maven issue is probably triggered by my Yetus hack that runs mvn verify
during precommit (Yetus is not meant to do that originally). Fixing that will
not be easy.
Can you open a new ticket for that problem with your analysis ?
The test execution time penalty however looks a bit scary, though the variance
on the Jenkins executors is huge.
Can you run a direct comparison between the forkCount cases on a physical
machine or a "real" VM where the runtime comparisons are meaningful ?
was (Author: stoty):
This is great, [~vjasani]
The maven issue is probably triggered by my Yetus hack that runs mvn verify
during precommit (Yetus is not meant to do that originally). Fixing that will
not be easy.
Can you open a new ticket for that problem with your analysis ?
The test execution time penalty however looks a bit scary, though the variance
on the Jenkins executors is huge.
Can you run a direct comparison between the forkCount cases on a physical
machine or a "real" VM where the runtime comparisons are meaningful ?
(Keeping mind that they the test execution ordering can also affect the
runtime, which depends on how the filesystem naturally orders them, so they are
best run on the same physical directory, or changing the maven execution order
to alphabetical)
> 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)
