delta/gitlab/gitlab-ce.git - gitlab.com: gitlab-org/gitlab-ce.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add latest changes from gitlab-org/gitlab@13-0-stable-ee	GitLab Bot	2020-05-20	1	-4/+4
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2019-11-13	1	-2/+2
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2019-09-26	1	-5/+5
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2019-09-18	1	-13/+45
\|
*	sidekiq: terminate child processes at shutdown	Nick Thomas	2019-03-04	1	-0/+5
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	Send SIGSTP before SIGTERM to actually give Sidekiq jobs 30s to finish when ↵dm-sidekiq-sigstp	Douwe Maan	2017-11-02	1	-3/+1
\| \| \| \|	the memory killer kicks in
*	Move operations/ to new locationdocs/refactor-operations	Achilleas Pipinellis	2016-10-11	1	-0/+40
	[ci skip]