Reply
New Contributor
Posts: 1
Registered: ‎01-04-2016

Impala JDBC Driver returns [Simba][ImpalaJDBCDriver](500151) Error setting/closing session: {0}

I am new to Cloudera, Hadoop and Impala. Apologies for anything.

 

Setup Detail:

CDH - 5.4.8

Impala - 2.2.0

Impala JDBC - 2.5.29

Kerberos Authentication

 

I am learning to test the performance of the cluster by executing Impala queries on CDH - 5.4.8 using Apache JMeter. JMeter provides support to execute queries on RDBMS using JDBC. So, I thought Impala JDBC could be a good option to test performance of Impala as well.

 

 

I followed the documentation at http://www.cloudera.com/content/www/en-us/documentation/enterprise/5-4-x/topics/impala_jdbc.html

 

Steps:

 

1. Download the Impala JDBC driver 2.5.29 and add to the Jmeter classpath [JMETER_HOME/lib/ext]

2. Create a test plan with 2 elements

    > JDBC configuration

        URL - jdbc:impala://<Data Node IP>:21050;principal=impala/master.localdomain@EXAMPLE.COM

        Driver - com.cloudera.impala.jdbc41.Driver [this was as per recommendation in the guide]

    > Sampler to execute a select query [select * from clear;]

3. Execute the test

 

While executing the test from jmeter, I get the following exception "[Simba][ImpalaJDBCDriver](500151) Error setting/closing session: {0}."  whereas, I am able to run the same query on the impala-shell without any errors.

Could you please help me figure out where I am doing wrong. Thanks

 

Successful on Impala-shell

qatest@edge:~> impala-shell -k -i node1
Starting Impala Shell using Kerberos authentication
Using service name 'impala'
Connected to node1:21000
Server version: impalad version 2.2.0-cdh5.4.8 RELEASE (build 137d99e9f751c454a0c79f3b00302938e4984f9c)
Welcome to the Impala shell. Press TAB twice to see a list of available commands.

Copyright (c) 2012 Cloudera, Inc. All rights reserved.

(Shell build version: Impala Shell v2.2.0-cdh5.4.8 (137d99e) built on Thu Oct 15 09:45:16 PDT 2015)
[node1:21000] > select * from clear;
Query: select * from clear
+---------------------+
| c1                  |
+---------------------+
| 67714081349158341   |
| 4917909736517554    |

 

Exception Trace while running from jmeter

 

2016/01/05 13:04:04 INFO  - jmeter.threads.ThreadGroup: Started thread group number 1
2016/01/05 13:04:04 INFO  - jmeter.engine.StandardJMeterEngine: All thread groups have been started
2016/01/05 13:04:04 INFO  - jmeter.threads.JMeterThread: Thread started: Thread Group 1-1
2016/01/05 13:04:05 WARN  - jmeter.protocol.jdbc.config.DataSourceElement: Could not return Connection java.sql.SQLException: [Simba][ImpalaJDBCDriver](500151) Error setting/closing session: {0}.
    at com.cloudera.hivecommon.api.HS2Client.openSession(Unknown Source)
    at com.cloudera.hivecommon.api.HS2Client.<init>(Unknown Source)
    at com.cloudera.hivecommon.api.HiveServer2ClientFactory.createClient(Unknown Source)
    at com.cloudera.hivecommon.core.HiveJDBCCommonConnection.connect(Unknown Source)
    at com.cloudera.jdbc.common.BaseConnectionFactory.doConnect(Unknown Source)
    at com.cloudera.jdbc.common.AbstractDriver.connect(Unknown Source)
    at java.sql.DriverManager.getConnection(DriverManager.java:664)
    at java.sql.DriverManager.getConnection(DriverManager.java:270)
    at org.apache.avalon.excalibur.datasource.JdbcConnectionFactory.newInstance(JdbcConnectionFactory.java:178)
    at org.apache.avalon.excalibur.pool.InstrumentedResourceLimitingPool.newPoolable(InstrumentedResourceLimitingPool.java:655)
    at org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.newPoolable(ValidatedResourceLimitingPool.java:145)
    at org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcConnectionPool.newPoolable(ResourceLimitingJdbcConnectionPool.java:91)
    at org.apache.avalon.excalibur.pool.InstrumentedResourceLimitingPool.get(InstrumentedResourceLimitingPool.java:371)
    at org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.get(ValidatedResourceLimitingPool.java:97)
    at org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcDataSource.getConnection(ResourceLimitingJdbcDataSource.java:188)
    at org.apache.jmeter.protocol.jdbc.config.DataSourceElement$DataSourceComponentImpl.getConnection(DataSourceElement.java:286)
    at org.apache.jmeter.protocol.jdbc.config.DataSourceElement.getConnection(DataSourceElement.java:146)
    at org.apache.jmeter.protocol.jdbc.sampler.JDBCSampler.sample(JDBCSampler.java:85)
    at org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:434)
    at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:261)
Caused by: com.cloudera.support.exceptions.GeneralException: [Simba][ImpalaJDBCDriver](500151) Error setting/closing session: {0}.
    ... 20 more
Caused by: org.apache.thrift.transport.TTransportException
    at org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:132)
    at org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
    at org.apache.thrift.protocol.TBinaryProtocol.readAll(TBinaryProtocol.java:378)
    at org.apache.thrift.protocol.TBinaryProtocol.readI32(TBinaryProtocol.java:297)
    at org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:204)
    at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:69)
    at org.apache.hive.service.cli.thrift.TCLIService$Client.recv_OpenSession(TCLIService.java:159)
    at com.cloudera.hivecommon.api.HS2ClientWrapper.recv_OpenSession(Unknown Source)
    at org.apache.hive.service.cli.thrift.TCLIService$Client.OpenSession(TCLIService.java:146)
    at com.cloudera.hivecommon.api.HS2ClientWrapper.OpenSession(Unknown Source)
    at com.cloudera.hivecommon.api.HS2Client.openSession(Unknown Source)
    at com.cloudera.hivecommon.api.HS2Client.<init>(Unknown Source)
    at com.cloudera.hivecommon.api.HiveServer2ClientFactory.createClient(Unknown Source)
    at com.cloudera.hivecommon.core.HiveJDBCCommonConnection.connect(Unknown Source)
    at com.cloudera.jdbc.common.BaseConnectionFactory.doConnect(Unknown Source)
    at com.cloudera.jdbc.common.AbstractDriver.connect(Unknown Source)
    at java.sql.DriverManager.getConnection(DriverManager.java:664)
    at java.sql.DriverManager.getConnection(DriverManager.java:270)
    at org.apache.avalon.excalibur.datasource.JdbcConnectionFactory.newInstance(JdbcConnectionFactory.java:178)
    at org.apache.avalon.excalibur.pool.InstrumentedResourceLimitingPool.newPoolable(InstrumentedResourceLimitingPool.java:655)
    at org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.newPoolable(ValidatedResourceLimitingPool.java:145)
    at org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcConnectionPool.newPoolable(ResourceLimitingJdbcConnectionPool.java:91)
    at org.apache.avalon.excalibur.pool.InstrumentedResourceLimitingPool.get(InstrumentedResourceLimitingPool.java:371)
    at org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.get(ValidatedResourceLimitingPool.java:97)
    at org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcDataSource.getConnection(ResourceLimitingJdbcDataSource.java:188)
    at org.apache.jmeter.protocol.jdbc.config.DataSourceElement$DataSourceComponentImpl.getConnection(DataSourceElement.java:286)
    at org.apache.jmeter.protocol.jdbc.config.DataSourceElement.getConnection(DataSourceElement.java:146)
    at org.apache.jmeter.protocol.jdbc.sampler.JDBCSampler.sample(JDBCSampler.java:85)
    at org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:434)
    at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:261)
    at java.lang.Thread.run(Thread.java:745)

2016/01/05 13:04:05 INFO  - jmeter.threads.JMeterThread: Thread is done: Thread Group 1-1
2016/01/05 13:04:05 INFO  - jmeter.threads.JMeterThread: Thread finished: Thread Group 1-1
2016/01/05 13:04:05 INFO  - jmeter.engine.StandardJMeterEngine: Notifying test listeners of end of test
2016/01/05 13:04:05 INFO  - jmeter.gui.util.JMeterMenuBar: setRunning(false,*local*)

New Contributor
Posts: 7
Registered: ‎07-17-2016

Re: Impala JDBC Driver returns [Simba][ImpalaJDBCDriver](500151) Error setting/closing session: {0}

Is anyone was able to figure any solution for the above issue ?
Announcements

Our community is getting a little larger. And a lot better.


Learn More about the Cloudera and Hortonworks community merger planned for late July and early August.