[jira] [Updated] (OOZIE-2175) Coord job with execution order LAST_ONLY/NONE can create enormous number of coord actions

[Purshotam Shah (JIRA)]

     [ 
https://issues.apache.org/jira/browse/OOZIE-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Purshotam Shah updated OOZIE-2175:
----------------------------------
    Description: 
Coord job with execution order LAST_ONLY/NONE doesn't respect Mat Throttling 
and can create enormous number of coord action.

If starttime is 2013 and current time is 2103 and job frequency is hourly, 
CoordMaterializeTransitionXCommand can create coord actions >10K in one 
materialization cycle.

{code}
        // If LAST_ONLY and all materialization is in the past, ignore 
maxActionsToBeCreated
        boolean ignoreMaxActions =
                
(coordJob.getExecutionOrder().equals(CoordinatorJob.Execution.LAST_ONLY) ||
                        
coordJob.getExecutionOrder().equals(CoordinatorJob.Execution.NONE))
                        && endMatdTime.before(new Date());

        while (effStart.compareTo(end) < 0 && (ignoreMaxActions || 
maxActionToBeCreated-- > 0)) {
            if (pause != null && effStart.compareTo(pause) >= 0) {
                break;

{code}


> Coord job with execution order LAST_ONLY/NONE can create enormous number of 
> coord actions
> -----------------------------------------------------------------------------------------
>
>                 Key: OOZIE-2175
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2175
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Purshotam Shah
>
> Coord job with execution order LAST_ONLY/NONE doesn't respect Mat Throttling 
> and can create enormous number of coord action.
> If starttime is 2013 and current time is 2103 and job frequency is hourly, 
> CoordMaterializeTransitionXCommand can create coord actions >10K in one 
> materialization cycle.
> {code}
>         // If LAST_ONLY and all materialization is in the past, ignore 
> maxActionsToBeCreated
>         boolean ignoreMaxActions =
>                 
> (coordJob.getExecutionOrder().equals(CoordinatorJob.Execution.LAST_ONLY) ||
>                         
> coordJob.getExecutionOrder().equals(CoordinatorJob.Execution.NONE))
>                         && endMatdTime.before(new Date());
>         while (effStart.compareTo(end) < 0 && (ignoreMaxActions || 
> maxActionToBeCreated-- > 0)) {
>             if (pause != null && effStart.compareTo(pause) >= 0) {
>                 break;
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)