delta/gitlab/gitlab-ce.git/doc/operations/sidekiq_memory_killer.md, branch project-settings gitlab.com: gitlab-org/gitlab-ce.git Sidekiq MemoryKiller sends a `SIGKILL` signal, not `SIGTERM` 2016-04-26T13:46:54+00:00 Rémy Coutable remy@rymai.me 2016-04-26T13:46:06+00:00 cdf91da3ebb2ca8795ea88365792333a957e6cfa [ci skip] Signed-off-by: Rémy Coutable <remy@rymai.me> 
[ci skip]

Signed-off-by: Rémy Coutable <remy@rymai.me>
Add SIDEKIQ_MEMORY_KILLER_SHUTDOWN_SIGNAL env var 2015-05-07T16:47:03+00:00 Jacob Vosmaer contact@jacobvosmaer.nl 2015-05-07T16:47:03+00:00 1c1f18b416febb8296facca37dc7504c2da880f8 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. 
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.
Add documentation for the Sidekiq MemoryKiller 2014-12-15T12:43:36+00:00 Jacob Vosmaer contact@jacobvosmaer.nl 2014-12-15T12:43:36+00:00 71789468d306c7974fcf27442c83d7fc131e94fa