[
https://issues.apache.org/jira/browse/PHOENIX-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17262130#comment-17262130
]
Viraj Jasani edited comment on PHOENIX-6288 at 1/10/21, 9:13 AM:
-----------------------------------------------------------------
{quote}The test execution time penalty however looks a bit scary, though the
variance on the Jenkins executors is huge.
{quote}
[~stoty] The variance here means time difference b/ multiple Jenkins run right?
{quote}Can you run a direct comparison between the forkCount cases on a
physical machine or a "real" VM where the runtime comparisons are meaningful ?
{quote}
We just want to record time different?
The diff in build #2 and #3 on PR#1080 is:
{code:java}
[INFO] Phoenix Core ....................................... SUCCESS [ 04:13 h]
{code}
vs
{code:java}
[INFO] Phoenix Core ....................................... SUCCESS [ 03:33 h]
{code}
As per existing multibranch results:
[https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/master/192/consoleFull|https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/master/192/consoleFull:]
{code:java}
[INFO] Phoenix Core ....................................... SUCCESS [ 03:24 h]
{code}
[https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/master/191/consoleFull]
{code:java}
HBase 2.2:
[INFO] Phoenix Core ....................................... SUCCESS [ 03:34 h]
{code}
{code:java}
HBase 2.1:
[INFO] Phoenix Core ....................................... SUCCESS [ 01:46 h]
{code}
Similar pattern for rest of latest builds.
Basically for HBase 2.1 version (default run on PR builds), the patch is taking
more than 3/4 hr where multibranch results are taking less than 2 hr.
Although let me plan to compare them closely on a VM, would you like to create
a new branch from master on upstream and maybe we can put this patch there and
try to see how much time it's taking for all HBase 2.x versions?
was (Author: vjasani):
{quote}The test execution time penalty however looks a bit scary, though the
variance on the Jenkins executors is huge.
{quote}
[~stoty] The variance here means time difference b/ multiple Jenkins run right?
{quote}Can you run a direct comparison between the forkCount cases on a
physical machine or a "real" VM where the runtime comparisons are meaningful ?
{quote}
We just want to record time different?
The diff in build #2 and #3 on PR#1080 is:
{code:java}
[INFO] Phoenix Core ....................................... SUCCESS [ 04:13 h]
{code}
vs
{code:java}
[INFO] Phoenix Core ....................................... SUCCESS [ 03:33 h]
{code}
As per existing multibranch results:
[https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/master/192/consoleFull|https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/master/192/consoleFull:]
{code:java}
[INFO] Phoenix Core ....................................... SUCCESS [ 03:24 h]
{code}
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/master/191/consoleFull
{code:java}
[INFO] Phoenix Core ....................................... SUCCESS [ 03:34 h]
{code}
{code:java}
[INFO] Phoenix Core ....................................... SUCCESS [ 01:46 h]
{code}
Similar pattern for rest of latest builds.
Although let me plan to compare them closely on a VM, would you like to create
a new branch from master on upstream and maybe we can put this patch there and
try to see how much time it's taking for all HBase 2.x versions?
> 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)
