You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@oozie.apache.org by Jay Vyas <ja...@gmail.com> on 2014/02/17 23:46:40 UTC
Oozie reports "unkown hadoop job" failure ~ but no error indication
in YARN.
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/%3C19AD42E3F64F0F468A305399D0DF39D9335DAC6F34@winops07.win.compete.com%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(JavaActionExecutor.java:1009)
at
org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:177)
at
org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:56)
at org.apache.oozie.command.XCommand.call(XCommand.java:280)
at
org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
--
Jay Vyas
http://jayunit100.blogspot.com
Re: Oozie reports "unkown hadoop job" failure ~ but no error
indication in YARN.
Posted by Jay Vyas <ja...@gmail.com>.
thanks mona. YES We are still facing the issue. If we submit via
mapreduce the job definetly passes, because i can see the SUCCESS and
part-r-00000 files, but i still see failures.
thanks again for your response. I beleive someone else is seeing this on
Azure? We also see it in a non-HDFS file system setup.
On Thu, Mar 6, 2014 at 3:44 PM, Mona Chitnis <ch...@yahoo-inc.com> wrote:
> I think its a bug because you are just using simple java action. Are you
> submitting separate map-reduce jobs via your Java code? Then Oozie would
> not be able to get a pointer to those.
>
> Jay, are you still facing this issue or I have I missed the JIRA?
>
> ‹Mona
>
> On 2/18/14, 1:20 PM, "Jay Vyas" <ja...@gmail.com> wrote:
>
> >Sorry, i got my versions mixed up !
> >
> >oozie version 4.x
> >HADOOP version 2.2.0 :)
> >
> >
> >On Tue, Feb 18, 2014 at 3:19 PM, Mohammad Islam <mi...@yahoo.com>
> >wrote:
> >
> >> Oozie 2.2.0 is very old version. Is there any reason? I think you meant
> >> 3.2.0.
> >>
> >>
> >>
> >>
> >> On Tuesday, February 18, 2014 10:53 AM, Jay Vyas <ja...@gmail.com>
> >> wrote:
> >>
> >> 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 <ch...@yahoo-inc.com>
> >>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" <ja...@gmail.com> 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 <mi...@yahoo.com>
> >> >> wrote:
> >> >>
> >> >>> Which version of hadoop and oozie?
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>> On Tuesday, February 18, 2014 1:55 AM, Jay Vyas
> >><ja...@gmail.com>
> >> >>> 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 <gw...@gopivotal.com>
> >>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 <ja...@gmail.com>
> >> >>> 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
> >> >>> E3F64F0F468A305399D0DF39D9335DAC6F34@winops07.win.compete.com%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
> >> >
> >>
> >
> >
> >
> >--
> >Jay Vyas
> >http://jayunit100.blogspot.com
>
>
--
Jay Vyas
http://jayunit100.blogspot.com
Re: Oozie reports "unkown hadoop job" failure ~ but no error
indication in YARN.
Posted by Mona Chitnis <ch...@yahoo-inc.com>.
I think its a bug because you are just using simple java action. Are you
submitting separate map-reduce jobs via your Java code? Then Oozie would
not be able to get a pointer to those.
Jay, are you still facing this issue or I have I missed the JIRA?
‹Mona
On 2/18/14, 1:20 PM, "Jay Vyas" <ja...@gmail.com> wrote:
>Sorry, i got my versions mixed up !
>
>oozie version 4.x
>HADOOP version 2.2.0 :)
>
>
>On Tue, Feb 18, 2014 at 3:19 PM, Mohammad Islam <mi...@yahoo.com>
>wrote:
>
>> Oozie 2.2.0 is very old version. Is there any reason? I think you meant
>> 3.2.0.
>>
>>
>>
>>
>> On Tuesday, February 18, 2014 10:53 AM, Jay Vyas <ja...@gmail.com>
>> wrote:
>>
>> 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 <ch...@yahoo-inc.com>
>>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" <ja...@gmail.com> 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 <mi...@yahoo.com>
>> >> wrote:
>> >>
>> >>> Which version of hadoop and oozie?
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> On Tuesday, February 18, 2014 1:55 AM, Jay Vyas
>><ja...@gmail.com>
>> >>> 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 <gw...@gopivotal.com>
>>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 <ja...@gmail.com>
>> >>> 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
>> >>> E3F64F0F468A305399D0DF39D9335DAC6F34@winops07.win.compete.com%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
>> >
>>
>
>
>
>--
>Jay Vyas
>http://jayunit100.blogspot.com
Re: Oozie reports "unkown hadoop job" failure ~ but no error
indication in YARN.
Posted by Jay Vyas <ja...@gmail.com>.
Sorry, i got my versions mixed up !
oozie version 4.x
HADOOP version 2.2.0 :)
On Tue, Feb 18, 2014 at 3:19 PM, Mohammad Islam <mi...@yahoo.com> wrote:
> Oozie 2.2.0 is very old version. Is there any reason? I think you meant
> 3.2.0.
>
>
>
>
> On Tuesday, February 18, 2014 10:53 AM, Jay Vyas <ja...@gmail.com>
> wrote:
>
> 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 <ch...@yahoo-inc.com> 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" <ja...@gmail.com> 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 <mi...@yahoo.com>
> >> wrote:
> >>
> >>> Which version of hadoop and oozie?
> >>>
> >>>
> >>>
> >>>
> >>> On Tuesday, February 18, 2014 1:55 AM, Jay Vyas <ja...@gmail.com>
> >>> 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 <gw...@gopivotal.com> 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 <ja...@gmail.com>
> >>> 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
> >>> E3F64F0F468A305399D0DF39D9335DAC6F34@winops07.win.compete.com%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
> >
>
--
Jay Vyas
http://jayunit100.blogspot.com
Re: Oozie reports "unkown hadoop job" failure ~ but no error indication in YARN.
Posted by Mohammad Islam <mi...@yahoo.com>.
Oozie 2.2.0 is very old version. Is there any reason? I think you meant 3.2.0.
On Tuesday, February 18, 2014 10:53 AM, Jay Vyas <ja...@gmail.com> wrote:
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 <ch...@yahoo-inc.com> 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" <ja...@gmail.com> 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 <mi...@yahoo.com>
>> wrote:
>>
>>> Which version of hadoop and oozie?
>>>
>>>
>>>
>>>
>>> On Tuesday, February 18, 2014 1:55 AM, Jay Vyas <ja...@gmail.com>
>>> 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 <gw...@gopivotal.com> 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 <ja...@gmail.com>
>>> 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
>>> E3F64F0F468A305399D0DF39D9335DAC6F34@winops07.win.compete.com%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
>
Re: Oozie reports "unkown hadoop job" failure ~ but no error indication in YARN.
Posted by Jay Vyas <ja...@gmail.com>.
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 <ch...@yahoo-inc.com> 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" <ja...@gmail.com> 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 <mi...@yahoo.com>
>> wrote:
>>
>>> Which version of hadoop and oozie?
>>>
>>>
>>>
>>>
>>> On Tuesday, February 18, 2014 1:55 AM, Jay Vyas <ja...@gmail.com>
>>> 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 <gw...@gopivotal.com> 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 <ja...@gmail.com>
>>> 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
>>> E3F64F0F468A305399D0DF39D9335DAC6F34@winops07.win.compete.com%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
>
Re: Oozie reports "unkown hadoop job" failure ~ but no error
indication in YARN.
Posted by Mona Chitnis <ch...@yahoo-inc.com>.
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" <ja...@gmail.com> 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 <mi...@yahoo.com>
>wrote:
>
>> Which version of hadoop and oozie?
>>
>>
>>
>>
>> On Tuesday, February 18, 2014 1:55 AM, Jay Vyas <ja...@gmail.com>
>> 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 <gw...@gopivotal.com> 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 <ja...@gmail.com>
>>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
>>E3F64F0F468A305399D0DF39D9335DAC6F34@winops07.win.compete.com%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
Re: Oozie reports "unkown hadoop job" failure ~ but no error
indication in YARN.
Posted by Jay Vyas <ja...@gmail.com>.
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 <mi...@yahoo.com> wrote:
> Which version of hadoop and oozie?
>
>
>
>
> On Tuesday, February 18, 2014 1:55 AM, Jay Vyas <ja...@gmail.com>
> 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 <gw...@gopivotal.com> 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 <ja...@gmail.com> 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/%3C19AD42E3F64F0F468A305399D0DF39D9335DAC6F34@winops07.win.compete.com%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(JavaActionExecutor.java:1009)
> >> at
> >>
> >>
> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:177)
> >> at
> >>
> >>
> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:56)
> >> at org.apache.oozie.command.XCommand.call(XCommand.java:280)
> >> at
> >>
> >>
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
> >> at
> >>
> >>
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> >> at
> >>
> >>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> >> at java.lang.Thread.run(Thread.java:662)
> >>
> >>
> >>
> >>
> >> --
> >> Jay Vyas
> >> http://jayunit100.blogspot.com
> >
> >
> >
> > --
> > Regards
> > Gordon Wang
>
--
Jay Vyas
http://jayunit100.blogspot.com
Re: Oozie reports "unkown hadoop job" failure ~ but no error indication in YARN.
Posted by Mohammad Islam <mi...@yahoo.com>.
Which version of hadoop and oozie?
On Tuesday, February 18, 2014 1:55 AM, Jay Vyas <ja...@gmail.com> 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 <gw...@gopivotal.com> 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 <ja...@gmail.com> 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/%3C19AD42E3F64F0F468A305399D0DF39D9335DAC6F34@winops07.win.compete.com%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(JavaActionExecutor.java:1009)
>> at
>>
>> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:177)
>> at
>>
>> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:56)
>> at org.apache.oozie.command.XCommand.call(XCommand.java:280)
>> at
>>
>> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>> at
>>
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> at
>>
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:662)
>>
>>
>>
>>
>> --
>> Jay Vyas
>> http://jayunit100.blogspot.com
>
>
>
> --
> Regards
> Gordon Wang
Re: Oozie reports "unkown hadoop job" failure ~ but no error indication in YARN.
Posted by Jay Vyas <ja...@gmail.com>.
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 <gw...@gopivotal.com> 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 <ja...@gmail.com> 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/%3C19AD42E3F64F0F468A305399D0DF39D9335DAC6F34@winops07.win.compete.com%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(JavaActionExecutor.java:1009)
>> at
>>
>> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:177)
>> at
>>
>> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:56)
>> at org.apache.oozie.command.XCommand.call(XCommand.java:280)
>> at
>>
>> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>> at
>>
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> at
>>
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:662)
>>
>>
>>
>>
>> --
>> Jay Vyas
>> http://jayunit100.blogspot.com
>
>
>
> --
> Regards
> Gordon Wang
Re: Oozie reports "unkown hadoop job" failure ~ but no error
indication in YARN.
Posted by Gordon Wang <gw...@gopivotal.com>.
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 <ja...@gmail.com> 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/%3C19AD42E3F64F0F468A305399D0DF39D9335DAC6F34@winops07.win.compete.com%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(JavaActionExecutor.java:1009)
> at
>
> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:177)
> at
>
> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:56)
> at org.apache.oozie.command.XCommand.call(XCommand.java:280)
> at
>
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
>
>
>
>
> --
> Jay Vyas
> http://jayunit100.blogspot.com
>
--
Regards
Gordon Wang
Re: Oozie reports "unkown hadoop job" failure ~ but no error
indication in YARN.
Posted by Jay Vyas <ja...@gmail.com>.
To clarify, the exact exception message is:
Unknown hadoop job [job_1392665114408_0007] associated with action
[0000037-140217072450087-
oozie-oozi-W@java-node].
Any help would be appreciated.
On Mon, Feb 17, 2014 at 5:46 PM, Jay Vyas <ja...@gmail.com> 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/%3C19AD42E3F64F0F468A305399D0DF39D9335DAC6F34@winops07.win.compete.com%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(JavaActionExecutor.java:1009)
> at
> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:177)
> at
> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:56)
> at org.apache.oozie.command.XCommand.call(XCommand.java:280)
> at
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
>
>
>
>
> --
> Jay Vyas
> http://jayunit100.blogspot.com
>
--
Jay Vyas
http://jayunit100.blogspot.com