Apache Oozie Known Issues
— Oozie can't submit jobs to a secure MRv2 cluster if the Job History Server is down
After trying to submit the job (by default, three times), Oozie will SUSPEND the workflow automatically.
Severity: Low
Workaround:When you bring up the Job History Server, use the resume command to tell Oozie to continue the workflow from where it left off.
— An Oozie server works either with a Hadoop MRv1 cluster or a Hadoop YARN cluster, not both
Severity: Low
Anticipated Resolution: None planned
Workaround: Use two different Oozie servers
When you use Hive Server 2 from Oozie, Oozie won't collect or print out the Hadoop Job IDs of any jobs launched by Hive Server 2
Bug: None
Severity: Low
Workaround: You can get the Hadoop IDs from the Resource Manager or JobTracker.
<< Cloudera Impala Known Issues and Workarounds | Apache Parquet (incubating) Known Issues >> | |