summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2014-10-12 18:38:25 +0300
committerRichard Ipsum <richardipsum@fastmail.co.uk>2014-10-13 14:59:37 +0100
commitac25a0d6b5476e49ab67b04e7dc81c623ff39722 (patch)
treeee8577fd23fe4f3fd96f43a71bceade20c9e3f85
parentcc8eb995bdcfe492cde33f2dbe831810e660027a (diff)
downloadlorry-controller-ac25a0d6b5476e49ab67b04e7dc81c623ff39722.tar.gz
Remove now-obsolete ghost job removal script
Lorry Controller now deals with these automatically.
-rw-r--r--exterminate-jobs-whose-minion-is-lost22
1 files changed, 0 insertions, 22 deletions
diff --git a/exterminate-jobs-whose-minion-is-lost b/exterminate-jobs-whose-minion-is-lost
deleted file mode 100644
index 4e9ff01..0000000
--- a/exterminate-jobs-whose-minion-is-lost
+++ /dev/null
@@ -1,22 +0,0 @@
-#!/bin/sh
-#
-# Sometimes a MINION dies and never tells WEBAPP that a job is
-# finished. This makes the list of jobs grow to max size, which
-# stops WEBAPP from scheduling more jobs to run. This scripts
-# EXTERMINATEs such jobs. Do NOT run it casually, you MUST check
-# that it is OK to EXTERMINATE the job first. Davros has spoken.
-#
-# This is a STOPGAP until Lorry Controller deals with this
-# automatically.
-
-# Not using -e so that curl failing won't stop things. curl may
-# fail if the job isn't in the expected state. We want to
-# EXTERMINATE it anyway.
-set -u
-
-for jobid in "$@"
-do
- curl -s -X POST --data "job_id=$jobid" http://localhost:12765/1.0/stop-job
- curl -s -X POST --data "job_id=$jobid&exit=125&stdout=&stderr=" http://localhost:12765/1.0/job-update
- curl -s -X POST --data "job_id=$jobid" http://localhost:12765/1.0/remove-job
-done > /dev/null