Comment 4 for bug 1265068

Not that some of these failures can occur prior to the submission to oozie (configuration issues etc), in which case the problem may be more of an issue with propagation of exceptions to the appropriate layer.

— Jon

On Jan 7, 2014, at 4:07 AM, Matthew Farrellee <email address hidden> wrote:

> Seems like the options are to 0) find a way to detect a functional oozie
> or 1) decide on a timeout for pending
>
> I'd rather do (0), but a functioning oozie may still fail if the cluster
> itself is not functional. The only way to detect a functioning cluster
> is to run a simple job through oozie. However, a functioning cluster may
> only run one job before crashing, which means ultimately (1) is
> necessary.
>
> If urgent, I'd proceed w/ (1), after careful thought about what's too
> long of a PENDING wait.
>
> If not urgent or as a long term approach, we should look at doing a
> oozie status test and potentially running a simple job.
>
> --
> You received this bug notification because you are a member of Savanna,
> which is subscribed to Savanna.
> Matching subscriptions: Savanna bugs
> https://bugs.launchpad.net/bugs/1265068
>
> Title:
> [EDP] Execution stays 'Pending' after failure on oozie side
>
> Status in OpenStack Data Processing (Savanna):
> New
>
> Bug description:
> Steps to repro:
> 1. Misconfigure oozie (a lot of ways)
> 2. Run Job
>
> Observed behavior:
> Execution will remain in 'Pending' forever. No errors on Savanna side.
>
> Expected behavior:
> Execution moved to Error state.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/savanna/+bug/1265068/+subscriptions

--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.