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

Istvan Toth commented on PHOENIX-5769:
--------------------------------------

I could reproduce the hang in the test suite locally.

Whether it is a problem with the hanging test, or we simply run out of some 
resource at this point needs further investigation:

{noformat}
"main" #1 prio=5 os_prio=0 tid=0x00007f6ad004b000 nid=0x55aef waiting on 
condition [0x00007f6ad66c9000]
   java.lang.Thread.State: TIMED_WAITING (sleeping)
        at java.lang.Thread.sleep(Native Method)
        at 
org.apache.hadoop.hbase.client.HBaseAdmin$ProcedureFuture.waitProcedureResult(HBaseAdmin.java:3557)
        at 
org.apache.hadoop.hbase.client.HBaseAdmin$ProcedureFuture.get(HBaseAdmin.java:3487)
        at org.apache.hadoop.hbase.client.HBaseAdmin.get(HBaseAdmin.java:2197)
        at 
org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:642)
        at 
org.apache.phoenix.query.ConnectionQueryServicesImpl.ensureTableCreated(ConnectionQueryServicesImpl.java:1339)
        at 
org.apache.phoenix.query.ConnectionQueryServicesImpl.createTable(ConnectionQueryServicesImpl.java:1801)
        at 
org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClient.java:2960)
        at 
org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:1094)
        at 
org.apache.phoenix.compile.CreateTableCompiler$CreateTableMutationPlan.execute(CreateTableCompiler.java:383)
        at 
org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:415)
        at 
org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:397)
        at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
        at 
org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:396)
        at 
org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:384)
        at 
org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1886)
        at 
org.apache.phoenix.end2end.IndexToolTimeRangeIT.createTableAndIndex(IndexToolTimeRangeIT.java:72)
        at 
org.apache.phoenix.end2end.IndexToolTimeRangeIT.setup(IndexToolTimeRangeIT.java:60)
        - locked <0x0000000083006708> (a java.lang.Class for 
org.apache.phoenix.end2end.IndexToolTimeRangeIT)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
        at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
        at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
        at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
        at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
        at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
        at org.junit.rules.RunRules.evaluate(RunRules.java:20)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
        at org.junit.runners.Suite.runChild(Suite.java:128)
        at org.junit.runners.Suite.runChild(Suite.java:27)
        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
        at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
        at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
        at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
        at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
        at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
        at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
        at 
org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
        at 
org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
        at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
        at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
        at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125){noformat}


> Phoenix precommit Flapping HadoopQA Tests in master 
> ----------------------------------------------------
>
>                 Key: PHOENIX-5769
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5769
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Daniel Wong
>            Assignee: Istvan Toth
>            Priority: Major
>         Attachments: PHOENIX-5769.master.v1.patch, 
> PHOENIX-5769.master.v3.patch, consoleFull (1).html, consoleFull (2).html, 
> consoleFull (3).html, consoleFull (4).html, consoleFull (5).html, consoleFull 
> (6).html, consoleFull (7).html, consoleFull (8).html, consoleFull.html
>
>
> I was recently trying to commit changes to Phoenix for multiple issues and 
> were asked to get clean HadoopQA runs.  However, this took a huge effort as I 
> had to resubmit the same patch multiple times in order to get one "clean".  
> Looking at the errors the most common one were 3 "Multiple regions on 
> <hostname,regions>" and 3 for apache infra issues (host shutdown), 1 for 
> org.apache.hadoop.hbase.NotServingRegionException, 1 for 
> SnapshotDoesNotExistException.   See builds 
> [https://builds.apache.org/job/PreCommit-PHOENIX-Build/] here from 3540's to 
> 3560's.  In addition I see multiple builds running simultaneously, limiting 
> tests to running on 1 host should be configurable right?
> In addition I was recommended by [~yanxinyi] that master was less likely to 
> have issues getting a clean run than 4.x.  FYI [~ckulkarni]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to