You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Mona Chitnis (JIRA)" <ji...@apache.org> on 2013/12/04 01:53:35 UTC
[jira] [Created] (OOZIE-1632) Coordinators that undergo change
endtime but are doneMaterialization, not getting picked for StatusTransit
Mona Chitnis created OOZIE-1632:
-----------------------------------
Summary: Coordinators that undergo change endtime but are doneMaterialization, not getting picked for StatusTransit
Key: OOZIE-1632
URL: https://issues.apache.org/jira/browse/OOZIE-1632
Project: Oozie
Issue Type: Bug
Components: coordinator
Affects Versions: 4.0.0, trunk
Reporter: Mona Chitnis
Assignee: Mona Chitnis
Fix For: trunk
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.
--
This message was sent by Atlassian JIRA
(v6.1#6144)