diff options
| author | Stan Hu <stanhu@gmail.com> | 2019-03-04 21:05:47 +0300 |
|---|---|---|
| committer | Stan Hu <stanhu@gmail.com> | 2019-03-04 21:05:47 +0300 |
| commit | 5c80bbb33c12490bc5fa711642a40fc16bdb79a4 (patch) | |
| tree | 37469f16101018bb3fe1eb3728257fac6425da03 /doc | |
| parent | 088128e621d0a7d48e89e738348a4ec57d8a0e36 (diff) | |
| parent | f0c52df5e540e825be0babd04cc557f3f40cf1c6 (diff) | |
Merge branch '40396-sidekiq-in-process-group' into 'master'
sidekiq: terminate child processes at shutdown
See merge request gitlab-org/gitlab-ce!25669
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/administration/operations/sidekiq_memory_killer.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/administration/operations/sidekiq_memory_killer.md b/doc/administration/operations/sidekiq_memory_killer.md index cbffd883774..8eac42f2fe2 100644 --- a/doc/administration/operations/sidekiq_memory_killer.md +++ b/doc/administration/operations/sidekiq_memory_killer.md @@ -17,6 +17,11 @@ With the default settings, the MemoryKiller will cause a Sidekiq restart no more often than once every 15 minutes, with the restart causing about one minute of delay for incoming background jobs. +Some background jobs rely on long-running external processes. To ensure these +are cleanly terminated when Sidekiq is restarted, each Sidekiq process should be +run as a process group leader (e.g., using `chpst -P`). If using Omnibus or the +`bin/background_jobs` script with `runit` installed, this is handled for you. + ## Configuring the MemoryKiller The MemoryKiller is controlled using environment variables. |