[OOZIE-1632] Coordinators that undergo change endtime but are doneMaterialization, not getting picked for StatusTransit

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: trunk, 4.0.0
• Fix Version/s: 4.1.0
• Component/s: coordinator
• Assignee: Mona Chitnis
• Reporter: Mona Chitnis
• Created: 04/Dec/13 00:51
• Updated: 12/Jan/15 06:08
• Resolved: 08/Jan/14 22:27

Description

The coordinator 'change' utility to say, change endtime of a coordinator, makes
a terminal job Running again, but if all actions are materialized, sets
doneMaterialization to true, and keeps pending to true. So far so good.

However, the expectation is StatusTransitService will pick this job and make
its state terminal, if actions are in terminal states. But if the actions have
terminated before this service's lastCheckTime, such jobs are not picked up.
This leaves the coordinator(and its parent bundle action) forever running.

Note that coordinator actions are properly terminated. Its only the coord job
that stays in limbo.

Issue Links

• is duplicated by: OOZIE-1590 Coord status not updated
• links to: ReviewBoard