[
https://issues.apache.org/jira/browse/PHOENIX-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17262134#comment-17262134
]
Viraj Jasani edited comment on PHOENIX-6288 at 1/10/21, 9:30 AM:
-----------------------------------------------------------------
Perhaps we can also try for keeping only non-indexing IT tests in phoenix-core
and move indexing IT tests in other module (create a new one phoenix-index-it
?), and then we can also utilize --threads in mvn arg, which is 1 as of now
because we have every test requiring miniCluster in phoenix-core.
{code:java}
# Running with threads>1 seems to trigger some problem in the build, but since
we
# spend 80+% of the time in phoenix-core, it wouldn't help much anyway
extra="--threads=1 -DPhoenixPatchProcess -Dskip.embedded"
if [[ "${PATCH_BRANCH}" = 4* ]]; then
extra="${extra} -Dhttps.protocols=TLSv1.2"
fi
{code}
If we choose to go this route, we should also create new BaseTest (better let
Indexing IT tests manage their own HBaseTestingUtility instances: init() and
destroy() ).
This way at least we will start decoupling some tests based on logical groups
(indexing vs non-indexing might be a good start but if there is some better
idea, let's brainstorm that as well).
was (Author: vjasani):
Perhaps we can also try for keeping only non-indexing IT tests in phoenix-core
and mover indexing IT tests in other module (create a new one phoenix-index-it
?), and then we can also utilize --threads in mvn arg, which is 1 as of now
because we have every test requiring miniCluster in phoenix-core.
{code:java}
# Running with threads>1 seems to trigger some problem in the build, but since
we
# spend 80+% of the time in phoenix-core, it wouldn't help much anyway
extra="--threads=1 -DPhoenixPatchProcess -Dskip.embedded"
if [[ "${PATCH_BRANCH}" = 4* ]]; then
extra="${extra} -Dhttps.protocols=TLSv1.2"
fi
{code}
If we choose to go this route, we should also create new BaseTest (better let
Indexing IT tests manage their own HBaseTestingUtility instances: init() and
destroy() ).
This way at least we will start decoupling some tests based on logical groups
(indexing vs non-indexing might be a good start but if there is some better
idea, let's brainstorm that as well).
> 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)
