[
https://issues.apache.org/jira/browse/OOZIE-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated OOZIE-2001:
-------------------------------
Fix Version/s: (was: trunk)
4.2
> Workflow re-runs doesn't update coord action status
> ---------------------------------------------------
>
> Key: OOZIE-2001
> URL: https://issues.apache.org/jira/browse/OOZIE-2001
> Project: Oozie
> Issue Type: Bug
> Reporter: Shwetha G S
> Assignee: Jaydeep Vishwakarma
> Fix For: 4.2
>
> Attachments: OOZIE-2001-v1.patch, OOZIE-2001-v2.patch,
> OOZIE-2001-v3.patch, OOZIE-2001-v4.patch, OOZIE-2001-v5.patch,
> OOZIE-2001-v6.patch, OOZIE-2001-v7.patch, OOZIE-2001.patch, rerun-0.patch
>
>
> When a workflow is re-run, the corresponding coord action status is not
> updated and coord action stays in killed state. This gives wrong impression
> that coord action is not running which is not the case
> SignalXCommand:
> {code}
> // Changing to synchronous call from asynchronous queuing to prevent
> // undue delay from between end of previous and start of next action
> if (wfJob.getStatus() != WorkflowJob.Status.RUNNING
> && wfJob.getStatus() != WorkflowJob.Status.SUSPENDED) {
> // only for asynchronous actions, parent coord action's external
> id will
> // persisted and following update will succeed.
> updateParentIfNecessary(wfJob);
> new WfEndXCommand(wfJob).call(); // To delete the WF temp dir
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
