[
https://issues.apache.org/jira/browse/OOZIE-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1319:
---------------------------------
Attachment: OOZIE-1319.patch
I've had to re-work the approach that the original patch was taking. In the
original patch, it only looks at the currently READY actions; we actually want
to skip any unscheduled actions (i.e. READY or WAITING). So, when I was trying
it out, what was happening is that the actions didn't all become READY at the
same time, so it wasn't skipping any.
The new patch keeps the SKIPPED status stuff from the original patch, but we
now check when we materialize actions. Basically, whenever we materialize
action(s) we want to skip all but the latest unscheduled action.
> "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
>
>
> 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)
