You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "zhang (JIRA)" <ji...@apache.org> on 2015/05/28 13:59:18 UTC
[jira] [Commented] (OOZIE-1319) "LAST_ONLY" in execution control
for coordinator job still runs all the actions
[ https://issues.apache.org/jira/browse/OOZIE-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562744#comment-14562744 ]
zhang commented on OOZIE-1319:
------------------------------
[~bowenzhangusa] in 4.1.0 version，Only when i restart the server it will skipped the WAITING or READY job. And why i can't find the handleLastOnly method in 4.1.0-branche source code. Thanks
> "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
> Fix For: 4.1.0
>
> Attachments: OOZIE-1319.patch, 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.3.4#6332)