5.5. Known Issues for Oozie

  • Oozie workflows that contain Hive queries which run mapreduce jobs fail on secure clusters.

    Problem: There is a bug in Hive (HIVE-5618) where delegation tokens are requested for a user who does not have the ability to do so (such as when it is launched from Oozie).

    Workaround: Set the configuration parameter before any query statements in the script file are launched as part of the Hive action

    hive.server2.enable.doAs = false

    This parameter instructs Hive not to request delegation tokens, which should not be done when running under Oozie.

  • Oozie reports the job as failed when the app and job completed successfully when RM is restarted multiple times

    Problem: From the oozie log

     2013-10-05 23:04:58,952 DEBUG HadoopAccessorService:545 - USER[hrt_qa] GROUP[-] TOKEN[] APP[wordcount-wf] JOB[0000003-131005052220011-oozie-oozi-W] ACTION[0000003-131005052220011-oozie-oozi-W@wc] Checking
    if filesystem hdfs is supported
    2013-10-05 23:04:58,954  WARN MapReduceActionExecutor:542 - USER[hrt_qa] GROUP[-] TOKEN[] APP[wordcount-wf] JOB[0000003-131005052220011-oozie-oozi-W] ACTION[0000003-131005052220011-oozie-oozi-W@wc] Launch
    erMapper died, check Hadoop log for job [hor12n01.gq1.ygridcore.net:8032:job_1381013595258_0001]

    But this job and the application complete successfully.


loading table of contents...