[ 
https://issues.apache.org/jira/browse/PHOENIX-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261820#comment-17261820
 ] 

Viraj Jasani edited comment on PHOENIX-6288 at 1/9/21, 9:23 AM:
----------------------------------------------------------------

Yeah this is sad.
{code:java}
[ERROR] org.apache.phoenix.end2end.index.AlterIndexIT  Time elapsed: 0.01 s  
<<< ERROR!
java.lang.RuntimeException: java.io.IOException: Shutting down
        at org.apache.phoenix.query.BaseTest.initMiniCluster(BaseTest.java:554)
        at org.apache.phoenix.query.BaseTest.setUpTestCluster(BaseTest.java:453)
        at 
org.apache.phoenix.query.BaseTest.checkClusterInitialized(BaseTest.java:439)
        at org.apache.phoenix.query.BaseTest.setUpTestDriver(BaseTest.java:522)
        at org.apache.phoenix.query.BaseTest.setUpTestDriver(BaseTest.java:517)
        at 
org.apache.phoenix.end2end.ParallelStatsDisabledIT.doSetup(ParallelStatsDisabledIT.java:62)
        at sun.reflect.GeneratedMethodAccessor152.invoke(Unknown Source)
{code}
Just before this exception log, we have
{code:java}
[INFO] Running org.apache.phoenix.end2end.index.DropMetadataIT
[INFO] Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 277.381 
s - in org.apache.phoenix.end2end.UnionAllIT
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 34.317 s 
- in org.apache.phoenix.end2end.index.DropMetadataIT
[INFO] Running org.apache.phoenix.end2end.index.GlobalImmutableTxIndexIT
[INFO] Running org.apache.phoenix.end2end.index.AlterIndexIT
{code}
Does this mean GlobalImmutableTxIndexIT and AlterIndexIT are running in 
parallel? But in separate VMs?

*Edit:*

Both GlobalImmutableTxIndexIT and AlterIndexIT eventually extend 
ParallelStatsDisabledIT, which is of category ParallelStatsDisabledTest, and as 
per below comment reuseFork is true for ParallelStatsDisabledTest, so both of 
above tests were trying to initialize miniCluster in same VM. 

[~stoty] Do you think we should once try keeping reuseFork as *false* in 
pom.xml for PR#1078 just to see Jenkins build results? Whether resueFork should 
be false is something we can discuss on dev@ also because using same VM for 
initialing mini clusters for different tests can very well be an issue right?


was (Author: vjasani):
Yeah this is sad.
{code:java}
[ERROR] org.apache.phoenix.end2end.index.AlterIndexIT  Time elapsed: 0.01 s  
<<< ERROR!
java.lang.RuntimeException: java.io.IOException: Shutting down
        at org.apache.phoenix.query.BaseTest.initMiniCluster(BaseTest.java:554)
        at org.apache.phoenix.query.BaseTest.setUpTestCluster(BaseTest.java:453)
        at 
org.apache.phoenix.query.BaseTest.checkClusterInitialized(BaseTest.java:439)
        at org.apache.phoenix.query.BaseTest.setUpTestDriver(BaseTest.java:522)
        at org.apache.phoenix.query.BaseTest.setUpTestDriver(BaseTest.java:517)
        at 
org.apache.phoenix.end2end.ParallelStatsDisabledIT.doSetup(ParallelStatsDisabledIT.java:62)
        at sun.reflect.GeneratedMethodAccessor152.invoke(Unknown Source)
{code}
Just before this exception log, we have
{code:java}
[INFO] Running org.apache.phoenix.end2end.index.DropMetadataIT
[INFO] Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 277.381 
s - in org.apache.phoenix.end2end.UnionAllIT
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 34.317 s 
- in org.apache.phoenix.end2end.index.DropMetadataIT
[INFO] Running org.apache.phoenix.end2end.index.GlobalImmutableTxIndexIT
[INFO] Running org.apache.phoenix.end2end.index.AlterIndexIT
{code}
Does this mean GlobalImmutableTxIndexIT and AlterIndexIT are running in 
parallel? But in separate VMs?

> 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)

Reply via email to