[
https://issues.apache.org/jira/browse/OOZIE-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13992936#comment-13992936
]
Rohini Palaniswamy commented on OOZIE-1819:
-------------------------------------------
If it gets requeued because it is less than < 100ms, then it wastes 1 min. We
just had one user asking for 4 min latency jobs. This check would help a lot in
that case.
Just 100ms right? That should not be an issue. But if we really want to be
strict, we can queue CoordActionInputCheck with no delay (i.e checkDelay =
checkDelay < 0 ? 0 : checkDelay;). Another thing i noticed is that queue input
check is in storeToDB which is wrong. We should move it to performWrites() as
the action is actually stored to database only in performWrites(). Can you make
that change?
> 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)
