This error message will cause any issue with bundle change command.If you look
at the code, error message is thrown after calling DB update.
Can you check the bundle end time after change command and see if that is
changed? There could be other reasons which might be keeping bundle running.
From: Oren Mazor <[email protected]>
To: "[email protected]" <[email protected]>
Sent: Monday, August 31, 2015 12:36 PM
Subject: Killed coordinator keeping bundle from ending
Hey all,
I have a bundle where some jobs enter the killed state.
I attempt to update the endtime of the bundle, and this fails with:
< oozie-error-message: E1320: Bundle Job change error, [[
0001505-150826221231844-oozie-oozi-C : Coord is in killed state ][
0001496-150826221231844-oozie-oozi-C : Coord is in killed state ][
0001506-150826221231844-oozie-oozi-C : Coord is in killed state ][
0001514-150826221231844-oozie-oozi-C : Coord is in killed state ]]
The result is that all of the coordinators within it have terminated, but
the killed ones are keeping the bundle in the 'running' state because this
bit of code is only checking for the presence of results:
https://github.com/apache/oozie/blob/48b64bc9438137517e24b37b674c5a8893db67c3/core/src/main/java/org/apache/oozie/command/bundle/BundleJobChangeXCommand.java#L203
This is on oozie 4.1.0. Is the only solution to manually kill the bundle?
thanks!
Oren
