Oozie action error reporting

[John Armstrong <jr...@ccri.com>]

Hi everybody.

I'm writing a status-reporting method in my webapp that has some of its 
processing handled by Oozie on the back-end.  Basically, in such a case 
my program polls Oozie about the particular job, then chops the response 
down to the parts that would be useful to report.

When a java action dies due to an exception, the message in the 
exception is reported in the action's descriptor.  It would be nice to 
also have a stack trace, so I was wondering if that would be possible to 
include.  Without it we can use the Hadoop JobTracker URL to look 
through the logs by hand to find the exception, but reporting the full 
exception in the Oozie status would speed up diagnosis.

Re: Oozie action error reporting

[Mona Chitnis <ch...@yahoo-inc.com>]

Hello John,

This suggestion seems good and we will take a look into sufficiently
bubbling up the exception message to the java action error descriptor.

Thanks,
--
Mona Chitnis




On 7/19/12 6:29 AM, "John Armstrong" <jr...@ccri.com> wrote:

>Hi everybody.
>
>I'm writing a status-reporting method in my webapp that has some of its
>processing handled by Oozie on the back-end.  Basically, in such a case
>my program polls Oozie about the particular job, then chops the response
>down to the parts that would be useful to report.
>
>When a java action dies due to an exception, the message in the
>exception is reported in the action's descriptor.  It would be nice to
>also have a stack trace, so I was wondering if that would be possible to
>include.  Without it we can use the Hadoop JobTracker URL to look
>through the logs by hand to find the exception, but reporting the full
>exception in the Oozie status would speed up diagnosis.