[
https://issues.apache.org/jira/browse/OOZIE-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012582#comment-14012582
]
Bowen Zhang commented on OOZIE-1319:
------------------------------------
[~rkanter], I think my claim about problem arising from server backup is still
legit. Consider the server goes down at 8:30 am and back up at 9:31am. The job
has a frequency of 10 mins and starts at 8 am. what is expected is only the
action at 9:30 am should run and the rest should be skipped. But in your code,
the action at 8:50am would also run since CoordInputcheckXCommand sees the
nextcoordaction is null before the materialization service materializes actions
from 9 am till 10 am. As a result, the action at 8:50 am will be marked as
READY.
> "LAST_ONLY" in execution control for coordinator job still runs all the
> actions
> -------------------------------------------------------------------------------
>
> Key: OOZIE-1319
> URL: https://issues.apache.org/jira/browse/OOZIE-1319
> Project: Oozie
> Issue Type: Bug
> Reporter: Bowen Zhang
> Assignee: Robert Kanter
> Attachments: OOZIE-1319.patch, OOZIE-1319.patch, OOZIE-1319.patch,
> OOZIE-1319.patch, OOZIE-1319.patch, OOZIE-1319.patch, oozie-1319.patch
>
>
> In execute() of CoordJobGetReadyActionsJPAExecutor.java, once we retrieve the
> top item from a "LIFO" query result, we do not discard or delete the
> remaining items from the result list. As a result, the next time execute() is
> invoked, we will be retrieving the next item in line. Consequently, LAST_ONLY
> strategy will also execute all ready actions for a given coordinator job,
> making it no different than LIFO.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
