You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Virag Kothari (JIRA)" <ji...@apache.org> on 2012/06/25 19:45:42 UTC
[jira] [Updated] (OOZIE-885) A race condition can cause the
workflow/coordinator to run even after the bundle job is killed
[ https://issues.apache.org/jira/browse/OOZIE-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Virag Kothari updated OOZIE-885:
--------------------------------
Attachment: OOZIE-885.patch
BundleStatusCommand modified to account for when coord-id is null.
Recovery service modified to correctly log the error message.
Testing:
Patch verified by Y! qe
> A race condition can cause the workflow/coordinator to run even after the bundle job is killed
> ----------------------------------------------------------------------------------------------
>
> Key: OOZIE-885
> URL: https://issues.apache.org/jira/browse/OOZIE-885
> Project: Oozie
> Issue Type: Bug
> Reporter: Virag Kothari
> Assignee: Virag Kothari
> Fix For: trunk, 3.2.1
>
> Attachments: OOZIE-885.patch
>
>
> Steps to reproduce:
> 1) Start the bundle job with a bunch of coordinators
> 2) Immediately kill it
> Observation:
> Some coordinators still keep on running
> Reason:
> Bundle cannot kill a coordinator unless a coord-id is associated to it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira