- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Unknown HS2 problem when communicating with Thrift server.
- Labels:
-
Apache Oozie
-
Cloudera Manager
Created on ‎08-16-2018 11:13 PM - edited ‎09-16-2022 06:35 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am getting this error in Hive queries.CM shows hive service is up and running just fine without any exits. Recently had connected to Hive through Tableau as well. Usually happens around the same time in morning,
How do I fix this? What could be the issue? No heavy processing on server when this happens. very few and small queries running at the time it happens.
Log Upload Time: Fri Aug 17 11:29:53 +0530 2018 Log Length: 959 SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/opt/cloudera/parcels/CDH-5.10.1-1.cdh5.10.1.p0.10/jars/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/yarn/nm/filecache/1237/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory] Connecting to jdbc:hive2://ip-172-31-4-192.ap-south-1.compute.internal:10000/default Unknown HS2 problem when communicating with Thrift server. Error: Could not open client transport with JDBC Uri: jdbc:hive2://ip-172-31-4-192.ap-south-1.compute.internal:10000/default: java.net.SocketException: Connection reset (state=08S01,code=0) No current connection Intercepting System.exit(2) Failing Oozie Launcher, Main class [org.apache.oozie.action.hadoop.Hive2Main], exit code [2]
Created ‎08-20-2018 11:36 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you able to share the workflow.xml file?
Do you have kerberos enabled in the cluster?
Created ‎03-13-2021 07:29 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @EricL
This happens due to the hive server is not working or stopped due to some problem.
Restart the hive server with the below command and try again.
hive --service hiveserver2 &
Regards,
Dhirendra
