Sure! Why do you think it is a bug? How do you know it's not my ignorance :) ...?
> On Feb 18, 2014, at 1:43 PM, Mona Chitnis <[email protected]> wrote: > > I believe the versions are flipped :-) > oozie = 4.0.0 > hadoop = 2.2.0 > > > This seems like a bug. Do you mind opening a JIRA for it? > >> On 2/18/14, 2:35 AM, "Jay Vyas" <[email protected]> wrote: >> >> regarding job history server: >> >> I've confirmed that JobHistoryServer works for vanilla hadoop jobs (i.e. >> calc pi), by simply checking the JobHistory UI. After retirement and >> success, jobs show up there if run manually. >> >> regarding versions: >> >> oozie = 2.2.0 >> hadoop = 4.0.0 >> >> >> On Tue, Feb 18, 2014 at 5:03 AM, Mohammad Islam <[email protected]> >> wrote: >> >>> Which version of hadoop and oozie? >>> >>> >>> >>> >>> On Tuesday, February 18, 2014 1:55 AM, Jay Vyas <[email protected]> >>> wrote: >>> >>> Jobhistory server is indeed running AFAIK. Oddly, while oozie fails >>> because it said the job doesn't exist, the Job history server reports >>> that >>> the exact same job has succeeded... >>> >>> >>>> On Feb 18, 2014, at 1:53 AM, Gordon Wang <[email protected]> wrote: >>>> >>>> Hi, >>>> >>>> Do you configure mapreduce history server properly? >>>> From the error message "Unknown hadoop job", I suspect that your >>> history >>>> server might not work. >>>> >>>> >>>> >>>>> On Tue, Feb 18, 2014 at 6:46 AM, Jay Vyas <[email protected]> >>> wrote: >>>>> >>>>> Hi oozie! >>>>> >>>>> I've run into quite cryptic error when submitting a very simple java >>> action >>>>> (DemoJavaMain, just prints args out). >>>>> >>>>> *** Oozie is failing out with JA017: *** >>>>> >>>>> "Oozie cant find the hadoop job associated with it. " >>>>> >>>>> >>>>> *** I dont see any indication of why the Job id isnt recoverable by >>> oozie >>>>> **** >>>>> >>>>> It seems to be available in YARN.... Here are some more details: >>>>> >>>>> - I've tried increasing user-retry to 3, that did not work. >>>>> - YARN doesnt seem to report any failures: Yarn somehow "thinks" the >>> job >>>>> succeeded. >>>>> - I dont see any system outs from the job (which is all the >>> DemoJavaMain >>>>> does). >>>>> >>>>> *** Ive seen this unresolved in a few places online... any thoughts >>> on >>> how >>>>> to fix it? *** >>> http://hortonworks.com/community/forums/topic/oozie-unknown-hadoop-job/ >>> >>> http://mail-archives.apache.org/mod_mbox/oozie-user/201211.mbox/%3C19AD42 >>> [email protected]%3E >>>>> >>>>> >>>>> *** my specifc exception is below **** >>>>> >>>>> org.apache.oozie.action.ActionExecutorException: JA017: Unknown >>> hadoop >>> job >>>>> [job_1392665114408_0007] associated with action >>>>> [0000037-140217072450087-oozie-oozi-W@java-node]. Failing this >>> action! >>>>> at >>> >>> org.apache.oozie.action.hadoop.JavaActionExecutor.check(JavaActionExecuto >>> r.java:1009) >>>>> at >>> >>> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXComma >>> nd.java:177) >>>>> at >>> >>> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXComma >>> nd.java:56) >>>>> at org.apache.oozie.command.XCommand.call(XCommand.java:280) >>>>> at >>> >>> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(Callabl >>> eQueueService.java:175) >>>>> at >>> >>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor >>> .java:886) >>>>> at >>> >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.jav >>> a:908) >>>>> at java.lang.Thread.run(Thread.java:662) >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Jay Vyas >>>>> http://jayunit100.blogspot.com >>>> >>>> >>>> >>>> -- >>>> Regards >>>> Gordon Wang >> >> >> >> -- >> Jay Vyas >> http://jayunit100.blogspot.com >
