[
https://issues.apache.org/jira/browse/OOZIE-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13991632#comment-13991632
]
Shwetha G S commented on OOZIE-1819:
------------------------------------
{quote}
So right now even if the input is available we don't start execution until
nominal time. Worth revisiting some time.
{quote}
[~rohini] I don't think oozie should launch before scheduled time. Then
schedule time doesn't make sense anymore. Probably the coord can be scheduled
for earlier if thats what was required.
I will look at the test failures. Thanks for triggering the tests
> Avoid early queueing of CoordActionInputCheckXCommand
> -----------------------------------------------------
>
> Key: OOZIE-1819
> URL: https://issues.apache.org/jira/browse/OOZIE-1819
> Project: Oozie
> Issue Type: Bug
> Reporter: Shwetha G S
> Assignee: Shwetha G S
> Fix For: trunk
>
> Attachments: OOZIE-1819.patch, OOZIE-1819.patch, OOZIE-1819.patch
>
>
> Currently, when coord action is materialised, CoordActionInputCheckXCommand
> is queued immediately. If the action is materialised long before the nominal
> time, this unnecessarily keeps executing CoordActionInputCheckXCommand and
> re-queues till nominal time. Instead, CoordActionInputCheckXCommand can be
> queued with delay = (nominal time - now)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
