[jira] [Updated] (OOZIE-1578) Coordinator jobs with cron frequency should be invalidated if nothing would be materialized during run time

["Bowen Zhang (JIRA)" <ji...@apache.org>]

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

Bowen Zhang updated OOZIE-1578:
-------------------------------

    Description: If a user specifies a cron frequency that materializes nothing between start and end time, the coordinator job will remain "RUNNING" forever. This is due to the way we update coord jobs in StatusTransitService when we select coordinator jobs to be updated by last modified time of coordinator actions in function coordTransit(). A coordinator job with no materialized actions will never be selected to update the terminal status. This is not an issue before cron frequency is introduced since every coordinator job is guaranteed to have materialized actions.

> Coordinator jobs with cron frequency should be invalidated if nothing would be materialized during run time 
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-1578
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1578
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Bowen Zhang
>            Assignee: Bowen Zhang
>
> If a user specifies a cron frequency that materializes nothing between start and end time, the coordinator job will remain "RUNNING" forever. This is due to the way we update coord jobs in StatusTransitService when we select coordinator jobs to be updated by last modified time of coordinator actions in function coordTransit(). A coordinator job with no materialized actions will never be selected to update the terminal status. This is not an issue before cron frequency is introduced since every coordinator job is guaranteed to have materialized actions.



--
This message was sent by Atlassian JIRA
(v6.1#6144)