azkaban-aplcache

Fix bug in killed quick finish (#1518) If a job is actually …

9/29/2017 6:49:41 PM

3.36.0

not run at all, but it has been marked as killed, the right thing to do is set the status to KILLED. Otherwise the flow would get stuck because this job would send the JOB_FINISHED event with the unfinished status: KILLING.

Juho Autio

Commit: cb532be

Tree: 9f30aba

Parents: 3fe6d05

Changes

azkaban-exec-server/src/main/java/azkaban/execapp/JobRunner.java 2(+1 -1)

Details

azkaban-exec-server/src/main/java/azkaban/execapp/JobRunner.java 2(+1 -1)

diff --git a/azkaban-exec-server/src/main/java/azkaban/execapp/JobRunner.java b/azkaban-exec-server/src/main/java/azkaban/execapp/JobRunner.java
index d570c98..e320258 100644
--- a/azkaban-exec-server/src/main/java/azkaban/execapp/JobRunner.java
+++ b/azkaban-exec-server/src/main/java/azkaban/execapp/JobRunner.java
@@ -405,7 +405,7 @@ public class JobRunner extends EventHandler implements Runnable {
         nodeStatus = changeStatus(Status.SKIPPED, time);
         quickFinish = true;
       } else if (this.isKilled()) {
-        nodeStatus = changeStatus(Status.KILLING, time);
+        nodeStatus = changeStatus(Status.KILLED, time);
         quickFinish = true;
       }