[
https://issues.apache.org/jira/browse/OOZIE-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13981614#comment-13981614
]
Bowen Zhang commented on OOZIE-1319:
------------------------------------
Neither of the two scenarios are guaranteed to work.
* The first scenario, {quote}In other words, when materializing actions, if it
sees any previously materialized actions READY/WAITING, they'll be set to
SKIPPED.{quote} After oozie server is back up, when you run the second
materialization, previously materialized actions may already be in RUNNING
state or even "SUCCEEDED" state, therefore your "get_unscheduled_actions" query
won't retrieve them.
* Second scenario, what if the data dependency is fulfilled at 10:30am? All the
WAITING actions will be in "READY" state. You need to wait till 10:55am to kick
off your materialization logic.
* Third point, your "GET_UNSCHEDULED_ACTIONS" query is retrieving all actions
regardless the execution order of the parent coord jobs.
> "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
>
>
> 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)
