I believe an action should timeout only when all the data dependency
conditions are not satisfied.
Once the action is in READY state, it means that dependencies are
satisfied but the job is waiting to run (concurrency, oozie is shut down
etc.) and it should not be timedout.
Regards,
On Saturday 25 January 2014 12:15 AM, Virag Kothari wrote:
Hi Adrian,
Your observation is correct. The timeout only applies for actions in
WAITING. It would be great if you file a JIRA to fix the wrong doc.
Thanks,
virag
On 1/21/14 5:57 PM, "Adrian Liu" <[email protected]> wrote:
Hi,
I'm asking as I read this from the doc
http://oozie.apache.org/docs/4.0.0/CoordinatorFunctionalSpec.html#a6.6.1._
coord:currentint_n_EL_Function_for_Synchronous_Datasets:
* Timeout: A coordinator job can specify the timeout for its
coordinator actions, this is, how long the coordinator action will be in
WAITING or READY status before giving up on its execution.
But the doc also said:
* timeout: The maximum time, in minutes, that a materialized action
will be waiting for the additional conditions to be satisfied before
being discarded. A timeout of 0 indicates that at the time of
materialization all the other conditions must be satisfied, else the
action will be discarded. A timeout of 0 indicates that if all the input
events are not satisfied at the time of action materizlization, the
action should timeout immediately. A timeout of -1 indicates no timeout,
the materialized action will wait forever for the other conditions to be
satisfied. The default value is -1 .
During my test it seemed that oozie actions in READY status won't
timeout. So I'm a little confused. What's the correct behavior for
timeout in oozie? Thanks.
Thanks,
Adrian
