summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRémy Coutable <remy@rymai.me>2016-04-26 15:46:06 +0200
committerRémy Coutable <remy@rymai.me>2016-04-26 15:46:54 +0200
commitcdf91da3ebb2ca8795ea88365792333a957e6cfa (patch)
treea9ab04cf8e868393389a8173164ecf91d23206c1
parentf127edd012bd8b6f76ac67d69aadbd7d4837258f (diff)
downloadgitlab-ce-fix-operations-doc.tar.gz
Sidekiq MemoryKiller sends a `SIGKILL` signal, not `SIGTERM`fix-operations-doc
[ci skip] Signed-off-by: Rémy Coutable <remy@rymai.me>
-rw-r--r--doc/operations/sidekiq_memory_killer.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/operations/sidekiq_memory_killer.md b/doc/operations/sidekiq_memory_killer.md
index 811c2192a19..b5e78348989 100644
--- a/doc/operations/sidekiq_memory_killer.md
+++ b/doc/operations/sidekiq_memory_killer.md
@@ -36,5 +36,5 @@ The MemoryKiller is controlled using environment variables.
Existing jobs get 30 seconds to finish. After that, the MemoryKiller tells
Sidekiq to shut down, and an external supervision mechanism (e.g. Runit) must
restart Sidekiq.
-- `SIDEKIQ_MEMORY_KILLER_SHUTDOWN_SIGNAL`: defaults to 'SIGTERM'. The name of
+- `SIDEKIQ_MEMORY_KILLER_SHUTDOWN_SIGNAL`: defaults to `SIGKILL`. The name of
the final signal sent to the Sidekiq process when we want it to shut down.