Sidekiq MemoryKiller sends a SIGKILL
signal, not SIGTERM
[ci skip] Signed-off-by: Rémy Coutable <remy@rymai.me>
This commit is contained in:
parent
f127edd012
commit
cdf91da3eb
1 changed files with 1 additions and 1 deletions
|
@ -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.
|
||||
|
|
Loading…
Reference in a new issue