beeline issue :

746 views
Skip to first unread message

pk.4...@gmail.com

unread,
Sep 8, 2020, 2:01:16 PM9/8/20
to MR3
Hi ,

I logged into the HS2 pod/container and tried to start beeline. I am seeing too many concurrent connections issue:
20/09/08 17:24:17 [main]: WARN jdbc.HiveConnection: Failed to connect to hivemr3-hiveserver2-wn98l:9852
Unexpected end of file when reading from HS2 server. The root cause might be too many concurrent connections. Please ask the administrator to check the number of active connections, and adjust hive.server2.thrift.max.worker.threads if applicable.
Error: Could not open client transport with JDBC Uri: jdbc:hive2://hivemr3-hiveserver2-wn98l:9852/;;;: null (state=08S01,code=0)
Beeline version 3.1.2 by Apache Hive
[WARN] Failed to create directory: /home/hive/.beeline
No such file or directory

I am the only user logged into HS2. I had tried logged into 3-4 hours ago and it had worked.

Any ideas?

Thanks ,
- Praveen 

Sungwoo Park

unread,
Sep 9, 2020, 12:35:26 AM9/9/20
to MR3
Hello,

Usually you get the error message when Beeline fails to connect to HiveServer2. (The message 'too many concurrent connections' applies only to Apache Hive.)

Could you check the log of HiveServer2 when Beeline is executed? If no messages are printed, it means that Beeline does not reach HiveServer2 for some reason. If you are testing on AWS, checking the status of LoadBalancer may help.

Cheers,

--- Sungwoo

Reply all
Reply to author
Forward
0 new messages