[
https://issues.apache.org/jira/browse/OOZIE-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13981488#comment-13981488
]
Bowen Zhang commented on OOZIE-1319:
------------------------------------
The right logic change should really happen in CoordActionReadyXCommand instead
of materialization stage. Your new approach will not work in the following two
scenarios:
* If a coordinator job starts at 9am and ends at 12pm with frequency of 10
minutes. And oozie server is back up at 11am. It is supposed to only run the
action at 10:50 am and forward. However, your new code will run the action at
10:50am AS WELL AS the action at 9:50am.
* Same coordinator job with a data dependency and oozie server is always up.
The job starts at 9am, but the data dependency fulfills only at 11am. ALL
actions will run since they are all marked as "WAITING" and no logic in
CoordActionREadyXCommand.
> "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
>
>
> 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)
