Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Impala live install to AWS EC2, Can't connect with ODBC

avatar
New Contributor

We are trying to test an Impala setup which was installed via the Live  install to AWS.  We are able to connect to the site, even SSH tunnel to the EC2 servers and utilize the web based interface for queries and uploading.  So far have been unable to connect via ODBC setting up the Cloudera drivers on MacOS 10.10 Yosemite, the current iODBC drivers have been installed as well.  Trying to connect to the master node, the one the cloudera inteface runs from at port 21050...  Using SSL and the .pem from keypairs generated to connect with EC2.  we are able to ssh into the EC2 instance with the .pem file.

 

The log from the driver is

 Aug 05 13:02:49 INFO  1 Driver::LogVersions: SDK Version: 09.03.09.1009

Aug 05 13:02:49 INFO  1 Driver::LogVersions: DSII Version: 2.5.29.1009

Aug 05 13:02:49 INFO  1 Driver::Initialize: Database CHAR Encoding: UTF-8

Aug 05 13:02:49 INFO  1 Driver::Initialize: Database WCHAR Encoding: UTF-16LE

Aug 05 13:02:49 INFO  1 Driver::Initialize: ANSI CHAR Encoding: US-ASCII

Aug 05 13:02:49 INFO  1 Driver::Initialize: Driver Manager WCHAR Encoding: UTF-32LE

Aug 05 13:02:49 INFO  1 Driver::Initialize: Locale name: en_US_POSIX

Aug 05 13:02:49 INFO  1 Driver::Initialize: Bitness: 64-bit

Aug 05 13:02:49 INFO  1 CInterface::SQLAllocHandle: Allocating environment handle.

Aug 05 13:02:49 INFO  1 Environment::SQLSetEnvAttr: Attribute: SQL_ATTR_ODBC_VERSION (200)

Aug 05 13:02:49 INFO  1 EnvironmentAttributes::SetAttribute: Setting ODBC version to: 3

Aug 05 13:02:49 INFO  1 CInterface::SQLAllocHandle: Allocating connection handle.

Aug 05 13:02:49 ERROR 1 Connection::SQLDriverConnectW: [Cloudera][ImpalaODBC] (100) Error from the Impala \

Thrift API: SSL_CTX_load_verify_locations: error code: 0

Aug 05 13:13:19 INFO  1 CInterface::SQLAllocHandle: Allocating environment handle.

Aug 05 13:13:19 INFO  1 Environment::SQLSetEnvAttr: Attribute: SQL_ATTR_ODBC_VERSION (200)

Aug 05 13:13:19 INFO  1 EnvironmentAttributes::SetAttribute: Setting ODBC version to: 3

Aug 05 13:13:19 INFO  1 CInterface::SQLAllocHandle: Allocating connection handle.

Aug 05 13:13:19 ERROR 1 Connection::SQLDriverConnectW: [Cloudera][ImpalaODBC] (100) Error from the Impala \

Thrift API: SSL_CTX_load_verify_locations: No such process

Aug 05 13:18:35 INFO  1 Driver::LogVersions: SDK Version: 09.03.09.1009

Aug 05 13:18:35 INFO  1 Driver::LogVersions: DSII Version: 2.5.29.1009

Aug 05 13:18:35 INFO  1 Driver::Initialize: Database CHAR Encoding: UTF-8

Aug 05 13:18:35 INFO  1 Driver::Initialize: Database WCHAR Encoding: UTF-16LE

Aug 05 13:18:35 INFO  1 Driver::Initialize: ANSI CHAR Encoding: US-ASCII

Aug 05 13:18:35 INFO  1 Driver::Initialize: Driver Manager WCHAR Encoding: UTF-32LE

Aug 05 13:18:35 INFO  1 Driver::Initialize: Locale name: en_US_POSIX

Aug 05 13:18:35 INFO  1 Driver::Initialize: Bitness: 64-bit

Aug 05 13:18:35 INFO  1 CInterface::SQLAllocHandle: Allocating environment handle.

Aug 05 13:18:35 INFO  1 Environment::SQLSetEnvAttr: Attribute: SQL_ATTR_ODBC_VERSION (200)

Aug 05 13:18:35 INFO  1 EnvironmentAttributes::SetAttribute: Setting ODBC version to: 3

Aug 05 13:18:35 INFO  1 CInterface::SQLAllocHandle: Allocating connection handle.

Aug 05 13:18:35 ERROR 1 Connection::SQLDriverConnectW: [Cloudera][ImpalaODBC] (100) Error from the Impala \

Thrift API: SSL_CTX_load_verify_locations: error code: 0

 

Thanks

Paul

1 ACCEPTED SOLUTION

avatar
New Contributor

Discovered our problem.  The master node is running Hive but not Impala.  The slave nodes are running Impala.  Had to open port 21050 on a slave node and connect to the slave node instead of the master node.  This fact was not well documented or was just assumed to be know to users.  Once we had the port open and pointing to the public dns name of a slave node all was good.

View solution in original post

2 REPLIES 2

avatar
New Contributor

Discovered our problem.  The master node is running Hive but not Impala.  The slave nodes are running Impala.  Had to open port 21050 on a slave node and connect to the slave node instead of the master node.  This fact was not well documented or was just assumed to be know to users.  Once we had the port open and pointing to the public dns name of a slave node all was good.

avatar
Community Manager

Congratulations on finding the solution to your issue and thank you for sharing it. Hopefully it will help others with a similar problem.


Cy Jervis, Manager, Community Program
Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.