[
https://issues.apache.org/jira/browse/OOZIE-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13991302#comment-13991302
]
Purshotam Shah commented on OOZIE-1819:
---------------------------------------
{quote}
Ah. Did not realize the check in CoordActionInputCheckXCommand. So right now
even if the input is available we don't start execution until nominal time.
Worth revisiting some time.
{quote}
Same for me. It didn't notice that we have current time check for
CoordActionInputCheckXCommand. It's not part of verifyPrecondition, so hard to
notice. Even if actions are created, inputchcek doesn't start before nominal
time, so it won't impact throttling.
{quote}
Now we have different setting for schedulingInterval and lookup interval.
If schedulingInterval > lookupInterval, then we should delay
CoordMaterializeTransitionXCommand for schedulingInterval - lookupInterval.
{quote}
Ignore this. I was trying to say that when server has huge load, we can
Materialize coord much before, but delay until lookupInterval. It's not
possible with current setting.
> 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
>
>
> 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)
