Viraj Jasani created PHOENIX-7964:
-------------------------------------

             Summary: Wait for system tables to initialize before starting REST 
server
                 Key: PHOENIX-7964
                 URL: https://issues.apache.org/jira/browse/PHOENIX-7964
             Project: Phoenix
          Issue Type: Test
            Reporter: Viraj Jasani


Before we start the REST server in each test, we should provide enough time for 
all system tables to come up.

Not doing this sometimes lead to errors like this:
{code:java}
org.apache.phoenix.exception.PhoenixIOException: SYSTEM.CATALOG
        at 
org.apache.phoenix.util.ClientUtil.parseServerException(ClientUtil.java:72)
        at 
org.apache.phoenix.query.ConnectionQueryServicesImpl.metaDataCoprocessorExec(ConnectionQueryServicesImpl.java:2424)
        at 
org.apache.phoenix.query.ConnectionQueryServicesImpl.metaDataCoprocessorExec(ConnectionQueryServicesImpl.java:2370)
        at 
org.apache.phoenix.query.ConnectionQueryServicesImpl.getTable(ConnectionQueryServicesImpl.java:2670)
        at 
org.apache.phoenix.schema.MetaDataClient.updateCache(MetaDataClient.java:608)
        at 
org.apache.phoenix.schema.MetaDataClient.updateCache(MetaDataClient.java:484)
        at 
org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:482)
        at 
org.apache.phoenix.jdbc.PhoenixStatement$1.call(PhoenixStatement.java:362)
        at org.apache.phoenix.call.CallRunner.run(CallRunner.java:52)
        at 
org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:362)
        at 
org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:348)
        at 
org.apache.phoenix.jdbc.PhoenixStatement.executeQuery(PhoenixStatement.java:2642)
        at 
org.apache.phoenix.ddb.rest.RESTServer.validateConnection(RESTServer.java:296)
        at org.apache.phoenix.ddb.rest.RESTServer.run(RESTServer.java:172)
        at 
org.apache.phoenix.ddb.GetRecordsTTLExpiryIT.initialize(GetRecordsTTLExpiryIT.java:116)
        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:59)
        at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
        at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
        at 
org.junit.internal.runners.statements.RunBefores.invokeMethod(RunBefores.java:33)
        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.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
        at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:377)
        at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:284)
        at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:248)
        at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:167)
        at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:456)
        at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:169)
        at 
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:595)
        at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:581)
Caused by: org.apache.hadoop.hbase.TableNotFoundException: SYSTEM.CATALOG
        at 
org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegionInMeta(ConnectionImplementation.java:1026)
        at 
org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:897)
        at 
org.apache.hadoop.hbase.client.HRegionLocator.lambda$getRegionLocation$0(HRegionLocator.java:80)
        at 
org.apache.hadoop.hbase.client.HRegionLocator.tracedLocationFuture(HRegionLocator.java:162)
        at 
org.apache.hadoop.hbase.client.HRegionLocator.getRegionLocation(HRegionLocator.java:79)
        at 
org.apache.hadoop.hbase.client.RegionLocator.getRegionLocation(RegionLocator.java:71)
        at 
org.apache.hadoop.hbase.client.HTable.getKeysAndRegionsInRange(HTable.java:283)
        at 
org.apache.hadoop.hbase.client.HTable.getKeysAndRegionsInRange(HTable.java:258)
        at 
org.apache.hadoop.hbase.client.HTable.getStartKeysInRange(HTable.java:1170)
        at 
org.apache.hadoop.hbase.client.HTable.lambda$coprocessorService$23(HTable.java:1132)
        at org.apache.hadoop.hbase.trace.TraceUtil.trace(TraceUtil.java:187)
        at 
org.apache.hadoop.hbase.client.HTable.coprocessorService(HTable.java:1128)
        at 
org.apache.hadoop.hbase.client.HTable.coprocessorService(HTable.java:1114)
        at 
org.apache.phoenix.query.ConnectionQueryServicesImpl.metaDataCoprocessorExec(ConnectionQueryServicesImpl.java:2395)
        ... 33 more
 {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to