An error occurred fetching the project authors.
- 22 Aug, 2019 1 commit
-
-
Thong Kuah authored
Using the sed script from https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
-
- 30 Jul, 2019 1 commit
-
-
Shinya Maeda authored
-
- 25 Jul, 2019 1 commit
-
-
Shinya Maeda authored
Currently, SidekiqMemoryKiller does not feed worker class name in the json structured logging. This commit extends the json parameter.
-
- 09 Mar, 2019 1 commit
-
-
Nick Thomas authored
-
- 04 Mar, 2019 1 commit
-
-
Nick Thomas authored
Sidekiq jobs frequently spawn long-lived child processes to do work. In some circumstances, these can be reparented to init when sidekiq is terminated, leading to duplication of work and strange concurrency problems. This commit changes sidekiq so that, if run as a process group leader, it will forward `INT` and `TERM` signals to the whole process group. If the memory killer is active, it will also use the process group when resorting to `kill -9` to shut down. These changes mean that a naive `kill <pid-of-sidekiq>` will now do the right thing, killing any child processes spawned by sidekiq, as long as the process supervisor placed it in its own process group. If sidekiq isn't a process group leader, this new code is skipped.
-
- 01 Mar, 2019 1 commit
-
-
Nick Thomas authored
-
- 28 Feb, 2019 1 commit
-
-
Nick Thomas authored
This reverts commit 00675311.
-
- 26 Feb, 2018 1 commit
-
-
Jacob Vosmaer (GitLab) authored
-
- 02 Nov, 2017 1 commit
-
-
Douwe Maan authored
Send SIGSTP before SIGTERM to actually give Sidekiq jobs 30s to finish when the memory killer kicks in
-