Oozie Jobs Fail With Different Errors Depending On User Submitting The Job in a Kerberized Cluster
(Doc ID 1927797.1)
Last updated on NOVEMBER 08, 2022
Applies to:
Big Data Appliance Integrated Software - Version 3.0.1 and laterLinux x86-64
Symptoms
NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.
Running Hive jobs from the CLI and from Hue work successfully in a kerberized cluster, but using Oozie/Hive for the same jobfails.
STDERR from the failing task:
Logging initialized using configuration in jar:file:/mapredpath/mapred/local/taskTracker/distcache/-100329414513428725_-281533297_1759649174/hostname/user/oozie/share/lib/hive/hive-common-0.10.0-cdh4.3.0.jar!/hive-log4j.properties
Hive history file=/tmp//hive_job_log_257aae88-b3e2-4cfb-87b2-04725f5096bd_443035871.txt
FAILED: Error in metadata: java.lang.RuntimeException: Unable to instantiate org.apache.hadoop.hive.metastore.HiveMetaStoreClient
FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask
Log file: /mapredpath/mapred/local/taskTracker/i53531/jobcache/job_201307161828_0064/attempt_201307161828_0064_m_000000_0/work/hive-oozie-job_201307161828_0064.log not present. Therefore no Hadoop jobids found
Intercepting System.exit(1)
Failing Oozie Launcher, Main class [org.apache.oozie.action.hadoop.HiveMain], exit code [1]
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |