[OOZIE-1578] Coordinator jobs with cron frequency should be invalidated upon submission if nothing would be materialized during run time - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 4.1.0
Component/s: None
Labels:
None

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.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

oozie-1578.patch
18/Oct/13 20:56
8 kB
Bowen Zhang

Activity

People

Assignee:: Bowen Zhang

Reporter:: Bowen Zhang

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 16/Oct/13 21:35

Updated:: 09/Dec/14 00:45

Resolved:: 18/Oct/13 22:41