[
https://issues.apache.org/jira/browse/OOZIE-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003922#comment-14003922
]
Robert Kanter commented on OOZIE-1319:
--------------------------------------
Looking at this again from another perspective: isn't setting LAST_ONLY
effectively equivalent to doing FIFO with a timeout set to the amount of time
between actions? For example, if you have actions materializing every 10min
and also have a timeout of 10min, then when the time dependency for the next
action is met, the previous action would become TIMEDOUT. This behavior
already exists. So, perhaps we can re-use that logic so that when LAST_ONLY is
set, the timeout for the {{current_action}} is set to
{{MIN(timeout_set_by_the_user, next_action.nominal_time –
current_action.nominal_time)}}? We then wouldn't need most of the other
changes I've already made and we'd reuse the TIMEDOUT status instead of the new
SKIPPED status.
Thoughts?
> "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
>
>
> 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)
