Support Questions
Find answers, ask questions, and share your expertise

Unknown HS2 problem when communicating with Thrift server.

We have been getting this error out of nowhere without having made any changes from past few days in some specific hours of the day. what could be the issue? My hive server is up and running without any issues and has not gone down either. This is when hive queries are running through oozie.

The error goes away after an hour or so on its own

<br>
            Log Upload Time: Tue Aug 14 12:02:46 +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/1002/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]
0 REPLIES 0