Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Beeline connection with Imapla error

Beeline connection with Imapla error

Rising Star

Hi ,

getting error while connecting to impala from beeline . host and ports are open . pls suggest 

 

[25761081@wuwcc9hddn01 ~]$ beeline -u "jdbc:hive2://hostname:25000/;principal=impala/hostname@CDH.PROD.COM"
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512M; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512M; support was removed in 8.0
scan complete in 4ms
Connecting to jdbc:hive2://hostname:25000/;principal=impala/hostname@CDH.PROD.COM
Error: Could not open client transport with JDBC Uri: jdbc:hive2://hostname:25000/;principal=impala/hostname@CDH.PROD.COM: java.net.ConnectException: Connection refused (state=08S01,code=0)
Beeline version 1.1.0-cdh5.7.5 by Apache Hive
0: jdbc:hive2://hostname:2 (closed)>

5 REPLIES 5
Highlighted

Re: Beeline connection with Imapla error

Contributor

 

beeline -u "jdbc:hive2://hostname:25000/;principal=impala/hostname@CDH.PROD.COM"

 

Port should be 21050(jdbc client port) and not 25000(webui port) and hostname should match the hostname of the impalad to which you connect.

 

beeline -u "jdbc:hive2://hostname:21050/;principal=impala/hostname@CDH.PROD.COM"

 

if you are using loadbalancer then the hostname should match the hostname of the loadbalancer

 

Re: Beeline connection with Imapla error

Rising Star
Thanks venkat
My bad yes i used the port 21050 and hostname is same to the impalad hostname but still the same error
beeline -u "jdbc:hive2://hostname:21050 /;principal=impala/hostname@CDH.PROD.COM"

Re: Beeline connection with Imapla error

Contributor

Can you please double check the principal used?

 

It should match exactly the value of "principal" property in the http://<impalad-hostname>:25000/varz page.

 

If you still face error in connecting inspite of using the correct principal name - then can you please post the error that you notice on the impalad logs

Re: Beeline connection with Imapla error

New Contributor

Got the same issue. Did you finally figure it out?

Re: Beeline connection with Imapla error

Rising Star
yeah its working for me but not sure now what was the problem . make sure firewall is open