[
https://issues.apache.org/jira/browse/OOZIE-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008687#comment-14008687
]
Shwetha G S commented on OOZIE-1819:
------------------------------------
Tests in error:
testCoordinatorActionCommandsSubmitAndStart(org.apache.oozie.sla.TestSLAEventGeneration):
E0605: Action does not exist [0000000-140524072412008-oozie-jenk-C@1]
testWorkflowActionRecoveryService(org.apache.oozie.service.TestRecoveryService):
E0607: Other error in operation [start], null
testCoordinatorActionEvent(org.apache.oozie.event.TestEventGeneration)
testUpdateCoordTableMultipleDepsV1(org.apache.oozie.command.coord.TestCoordPushDependencyCheckXCommand):
E1021: Coord Action Input Check Error: null
testCoordinatorActionCommandsSubmitAndStart(org.apache.oozie.sla.TestSLAEventGeneration)
fails on trunk itself. The rest pass on my box with the patch
> 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-v2.patch, OOZIE-1819-v3.patch,
> 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)
