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

["Mona Chitnis (JIRA)" <ji...@apache.org>]

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

Mona Chitnis updated OOZIE-1632:
--------------------------------

    Attachment: OOZIE-1632.patch

Fixes in CoordChangeXCommand and StatusTransitService (added JPAExecutor for a case to bring in coord jobs)

> 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: trunk, 4.0.0
>            Reporter: Mona Chitnis
>            Assignee: Mona Chitnis
>             Fix For: trunk
>
>         Attachments: OOZIE-1632.patch
>
>
> 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)