[
https://issues.apache.org/jira/browse/OOZIE-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13981821#comment-13981821
]
Robert Kanter commented on OOZIE-1319:
--------------------------------------
Here's a rough idea of what I'm currently thinking:
# When materializing actions in CoordMaterializeTransitionXCommand, if we're in
the past and LAST_ONLY, then it needs to materialize *all* actions until "now"
or the end of the job (whichever is earliest) and set all but the latest one to
SKIPPED (so we ignore the window in this case). And when materializing more
actions (at the next window), it should set any old WAITING ones to SKIPPED as
well. This doesn't touch any actions materialized in the future.
# When getting READY actions in CoordActionReadyXCommand, only the latest READY
action should become SUBMITTED; the rest should be SKIPPED (re-use LIFO query
here)
Just a note to clarify: even with LAST_ONLY it is possible for multiple jobs to
be RUNNING at the same time. e.g. if an older action that used to be the
latest is still RUNNING when new actions come along, then that older action and
the latest of the newer actions could both be RUNNING.
> "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)
