11-07-2018 08:40 AM - last edited on 11-08-2018 07:12 AM by cjervis
I've been configuring an Oozie hive2 action that simply drops a pre-existing table. I'm running this command from an .hql file and scheduling it with oozie on Hue.
For no apparent reason this job will sometimes work, but will also sporadically throw an error (stderr logs below):
Unknown HS2 problem when communicating with Thrift server. Error: Could not open client transport with JDBC Uri: jdbc:hive2://....
on port 10000 (state=08S01,code=0)
This ends with a system.exit(2) command. I've fiddled around with retry properties (max and interval) within the Hue workflow editor and this would appear to have an affect on my success rate, but the job still will not reliably work.
The relevant stdout logs are below:
<<< Invocation of Beeline command completed <<< No child hadoop job is executed. Intercepting System.exit(2) <<< Invocation of Main class completed <<< Failing Oozie Launcher, Main class [org.apache.oozie.action.hadoop.Hive2Main], exit code  Oozie Launcher failed, finishing Hadoop job gracefully
I should mention that is is running on a Kerberos Cluster. CDH-5.13.1, Hive2, Sqoop Version 1.4.6.
Are there any hive parameters that could be preventing a consistent, realible connection?? I've also checked the yarn logs, but to no avail. Has anyone experienced this error before??
11-08-2018 10:10 AM
When I try to run a single sqoop command with the hive table creation included in a single action I get the following error:
Logging initialized using configuration in jar:file:/u05/hadoop/yarn/nm/filecache/467/hive-exec.jar!/hive-log4j.properties FAILED: SemanticException org.apache.hadoop.hive.ql.metadata.HiveException: java.lang.RuntimeException: Unable to instantiate org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient Intercepting System.exit(1)