[jira] [Comment Edited] (OOZIE-2668) Status update and recovery problems when coord action and its children not in sync

["Satish Subhashrao Saley (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OOZIE-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15478108#comment-15478108 ] 

Satish Subhashrao Saley edited comment on OOZIE-2668 at 9/9/16 8:07 PM:
------------------------------------------------------------------------

Solution would be - If WF is already terminated skip queuing KillXCommand.


was (Author: satishsaley):
Solution would be - If WF is already terminated skip queuing KillXCommand,

> Status update and recovery problems when coord action and its children not in sync
> ----------------------------------------------------------------------------------
>
>                 Key: OOZIE-2668
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2668
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Satish Subhashrao Saley
>            Assignee: Satish Subhashrao Saley
>
> In cases where workflow is already in terminal status (except failed) but the coord action is not yet updated and still running, following will happen if a kill command is issued on the coord job: 
> Kill on Coordjob will make the kill on coordaction pending until the children are also killed. However, as the wf in terminal state (except failed), the wf will not be killed and preverifycondition will fail. The wf doesn't update its parent and hence the coordaction kill will still be pending. Two problems: Status transit service will not resolve the state of this coord job as some the actions are still pending Recovery service will try to recover this killed coord action and keep on reissuing the kill command.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)