diff options
| author | Jacob Vosmaer <contact@jacobvosmaer.nl> | 2015-05-07 18:47:03 +0200 |
|---|---|---|
| committer | Jacob Vosmaer <contact@jacobvosmaer.nl> | 2015-05-07 18:47:03 +0200 |
| commit | 1c1f18b416febb8296facca37dc7504c2da880f8 (patch) | |
| tree | 1db7a7015dcae8ba78cf133789bfccd6bd3c8d01 /doc/operations | |
| parent | 66f7cdeb0af70100b0c60163c4685ba671413ddd (diff) | |
| download | gitlab-ce-1c1f18b416febb8296facca37dc7504c2da880f8.tar.gz | |
Add SIDEKIQ_MEMORY_KILLER_SHUTDOWN_SIGNAL env var
It looks like SIGTERM may not be enough to shut down a Sidekiq process
when its RSS has gotten too big. This change will allow us to experiment
with sending SIGKILL instead of SIGTERM to Sidekiq processes on
gitlab.com.
Diffstat (limited to 'doc/operations')
| -rw-r--r-- | doc/operations/sidekiq_memory_killer.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/operations/sidekiq_memory_killer.md b/doc/operations/sidekiq_memory_killer.md index 867b01b0d5a..811c2192a19 100644 --- a/doc/operations/sidekiq_memory_killer.md +++ b/doc/operations/sidekiq_memory_killer.md @@ -36,3 +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 + the final signal sent to the Sidekiq process when we want it to shut down. |