- 21 Oct, 2016 1 commit
-
-
Yorick Peterse authored
Dumping too many jobs in the same queue (e.g. the "default" queue) is a dangerous setup. Jobs that take a long time to process can effectively block any other work from being performed given there are enough of these jobs. Furthermore it becomes harder to monitor the jobs as a single queue could contain jobs for different workers. In such a setup the only reliable way of getting counts per job is to iterate over all jobs in a queue, which is a rather time consuming process. By using separate queues for various workers we have better control over throughput, we can add weight to queues, and we can monitor queues better. Some workers still use the same queue whenever their work is related. For example, the various CI pipeline workers use the same "pipeline" queue. This commit includes a Rails migration that moves Sidekiq jobs from the old queues to the new ones. This migration also takes care of doing the inverse if ever needed. This does require downtime as otherwise new jobs could be scheduled in the old queues after this migration completes. This commit also includes an RSpec test that blacklists the use of the "default" queue and ensures cron workers use the "cronjob" queue. Fixes gitlab-org/gitlab-ce#23370
-
- 28 Apr, 2016 1 commit
-
-
Jacob Vosmaer authored
When running Unicorn or Sidekiq in the foreground this change removes an intermediate /bin/sh process. This makes process supervision in the GitLab Development Kit more reliable. This change does not affect Omnibus-GitLab (because there we do not use these launch scripts). Installations from source do use the launch scripts but for the standard GitLab init script this change will not make a difference. Custom installations using Upstart or Systemd may be affected however, because under certain configurations these systems count exactly how many forks happen during process startup, and we are reducing that number by one here.
-
- 15 Jan, 2016 1 commit
-
-
Jacob Vosmaer authored
This behavior got lost in the previous commit.
-
- 14 Jan, 2016 1 commit
-
-
Jacob Vosmaer authored
-
- 03 Dec, 2015 1 commit
-
-
Valery Sizov authored
-
- 26 Aug, 2015 1 commit
-
-
Douwe Maan authored
-
- 19 Aug, 2015 1 commit
-
-
Douwe Maan authored
-
- 01 Apr, 2015 1 commit
-
-
Douwe Maan authored
-
- 10 Sep, 2014 1 commit
-
-
Marin Jankovski authored
-
- 08 Sep, 2014 1 commit
-
-
Jacob Vosmaer authored
-
- 04 Jul, 2014 3 commits
-
-
Pavel Novitskiy authored
-
Pavel Novitskiy authored
-
ling.su authored
Delete mailer queue because we don't use sidekiq_mailer gem and now the mailer queue doesn't exist any more.
-
- 12 Jun, 2014 1 commit
-
-
Jacob Vosmaer authored
Avoid the background_jobs script killing every process with 'sidekiq' in its argument string (e.g. 'rake gitlab:sidekiq start') by also catching the number (2) in 'sidekiq 2.14'.
-
- 27 May, 2014 1 commit
-
-
Marin Jankovski authored
-
- 01 Apr, 2014 1 commit
-
-
Jacob Vosmaer authored
This syntax is compatible with the current Sidekiq version we use (2.17.0) and it protects us against future breakage by https://github.com/mperham/sidekiq/commit/040eda558bc64139c846c781d3de0b79603e3035
-
- 20 Mar, 2014 2 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
- 10 Feb, 2014 1 commit
-
-
Matthew Trisoline authored
Updated script/{web,background_job} to use #!/usr/bin/env bash rather than #!/bin/bash to allow for transparency between OS namely Linux and FreeBSD and for source installs of bash where path is not exported by default for /usr/local/{bin,sbin}
-
- 22 Oct, 2013 1 commit
-
-
Jacob Vosmaer authored
-
- 15 Oct, 2013 1 commit
-
-
Jacob Vosmaer authored
-