[
https://issues.apache.org/jira/browse/OOZIE-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012985#comment-14012985
]
Robert Kanter commented on OOZIE-1319:
--------------------------------------
That's going to get tricky. I have another idea to try first: Instead of
looking at the nominal time of the next action in
CoordActionInputCheckXCommand, I can have it calculate what the nominal time of
the next action should be. Functionally, this is equivalent to what I have
now, but the advantage is that it doesn't rely on the next action having been
materialized yet. So in the last scenario that you gave, even though the
action at 8:50am might see the nextcoordaction as null, it won't matter because
it will compute what the nextcoordaction's nominal time is. I should be able
to steal some logic from the CoordMaterializeTransitionXCommand for computing
the next nominal time.
> "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)
