[ 
https://issues.apache.org/jira/browse/PHOENIX-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajeshbabu Chintaguntla updated PHOENIX-1908:
---------------------------------------------
    Attachment: PHOENIX-1908.patch

Suspecting Phoenix driver might not loaded because of memory constraints. So 
getting this exception while creating connection. No other clue.
[~jamestaylor], [~samarthjain] Do you have any idea?
{noformat}
Caused by: java.sql.SQLException: No suitable driver found for 
jdbc:phoenix:localhost:50863;
        at java.sql.DriverManager.getConnection(DriverManager.java:596)
        at java.sql.DriverManager.getConnection(DriverManager.java:187)
        at org.apache.phoenix.util.QueryUtil.getConnection(QueryUtil.java:269)
        at org.apache.phoenix.util.QueryUtil.getConnection(QueryUtil.java:261)
        at 
org.apache.phoenix.coprocessor.MetaDataEndpointImpl$4.updateMutation(MetaDataEndpointImpl.java:1798)
        at 
org.apache.phoenix.coprocessor.MetaDataEndpointImpl.mutateColumn(MetaDataEndpointImpl.java:1532)
{noformat}

In the patch creating connection only when indexes are present otherwise it 
will be overhead. With this we should not get the test case failure because not 
indexes involved in the test case.

> TenantSpecificTablesDDLIT#testAddDropColumn is flaky
> ----------------------------------------------------
>
>                 Key: PHOENIX-1908
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1908
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Rajeshbabu Chintaguntla
>            Assignee: Rajeshbabu Chintaguntla
>             Fix For: 5.0.0, 4.4.0
>
>         Attachments: PHOENIX-1908.patch
>
>
> {noformat}
> Tests run: 18, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 39.262 sec 
> <<< FAILURE! - in org.apache.phoenix.end2end.TenantSpecificTablesDDLIT
> testAddDropColumn(org.apache.phoenix.end2end.TenantSpecificTablesDDLIT)  Time 
> elapsed: 8.529 sec  <<< ERROR!
> java.sql.SQLException: ERROR 2009 (INT11): Unknown error code 0
>         at 
> org.apache.phoenix.exception.SQLExceptionCode$Factory$1.newException(SQLExceptionCode.java:368)
>         at 
> org.apache.phoenix.exception.SQLExceptionInfo.buildException(SQLExceptionInfo.java:133)
>         at 
> org.apache.phoenix.exception.SQLExceptionCode.fromErrorCode(SQLExceptionCode.java:396)
>         at 
> org.apache.phoenix.util.ServerUtil.parseRemoteException(ServerUtil.java:127)
>         at 
> org.apache.phoenix.util.ServerUtil.parseServerExceptionOrNull(ServerUtil.java:115)
>         at 
> org.apache.phoenix.util.ServerUtil.parseServerException(ServerUtil.java:104)
>         at 
> org.apache.phoenix.query.ConnectionQueryServicesImpl.metaDataCoprocessorExec(ConnectionQueryServicesImpl.java:1022)
>         at 
> org.apache.phoenix.query.ConnectionQueryServicesImpl.dropColumn(ConnectionQueryServicesImpl.java:1738)
>         at 
> org.apache.phoenix.query.DelegateConnectionQueryServices.dropColumn(DelegateConnectionQueryServices.java:127)
>         at 
> org.apache.phoenix.query.DelegateConnectionQueryServices.dropColumn(DelegateConnectionQueryServices.java:127)
>         at 
> org.apache.phoenix.schema.MetaDataClient.dropColumn(MetaDataClient.java:2511)
>         at 
> org.apache.phoenix.jdbc.PhoenixStatement$ExecutableDropColumnStatement$1.execute(PhoenixStatement.java:901)
>         at 
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:298)
>         at 
> org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:290)
>         at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
>         at 
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:288)
>         at 
> org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:1163)
>         at 
> org.apache.phoenix.end2end.TenantSpecificTablesDDLIT.testAddDropColumn(TenantSpecificTablesDDLIT.java:238)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to