[
https://issues.apache.org/jira/browse/OOZIE-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990279#comment-13990279
]
Bowen Zhang commented on OOZIE-1319:
------------------------------------
[~chitnis], {quote}If materialization occurred at 10:55, why is 10:50 action
SKIPPED? it would be the last eligible action in this case right?{quote}, this
is the expected behavior, but not what his code is going to do. His new
function of handleLastOnly will mark all actions as "SKIPPED" during
materialization event.
{quote} e.g.
if action 10:50, n(SUBMITTED) = 0/1, own status - READY, action 10:40 -
SUBMITTED,
then action 10:40 -> SKIPPED, action 10:50 -> SUBMITTED
but, if action 10:50, n(SUBMITTED) = 1, own status - READY, action 10:40 -
RUNNING,
then action 10:50 would have to mark itself as SKIPPED right?
{quote}
These are all correct expected behavior. But the problem is in your first case,
marking action 10:40 from SUBMITTED to SKIPPED can't work 100% of the time
since at the mean time, RecoveryService may have already converted it into
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, 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)
