[ 
https://issues.apache.org/jira/browse/OOZIE-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990273#comment-13990273
 ] 

Mona Chitnis commented on OOZIE-1319:
-------------------------------------

bq. A job with frequency of 10 mins and starts from 10 am till 12 pm. Say, none 
of the data dependency is fulfilled. Your code will break if all of the data 
dependencies are fulfilled between 10:55 am and 11am. Since at 10:55 am, you 
SKIPPED all actions in the first hour 

If materialization occurred at 10:55, why is 10:50 action SKIPPED? it would be 
the last eligible action in this case right?

So we are going to have a case with multiple CoordActionReadyX commands queued 
up all looping over each other. To resolve this, you could have an action know 
the total SUBMITTED count so far and look only towards its predecessor. 
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?

> "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)

Reply via email to