summaryrefslogtreecommitdiff
path: root/bin/background_jobs
Commit message (Collapse)AuthorAgeFilesLines
* Re-organize queues to use for Sidekiqseparate-sidekiq-queuesYorick Peterse2016-10-211-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Use 'exec' in Unicorn and Sidekiq launch scriptsJacob Vosmaer2016-04-281-1/+1
| | | | | | | | | | | | | | | | 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.
* Direct sidekiq boot output to log filesimplify-procfileJacob Vosmaer2016-01-151-1/+1
| | | | This behavior got lost in the previous commit.
* Improve bin/ launchersJacob Vosmaer2016-01-141-2/+5
|
* Fix mailer queuefix_mailer_queueValery Sizov2015-12-031-1/+1
|
* Groundwork for merging CI into CEDouwe Maan2015-08-251-1/+1
|
* Update init scripts.Douwe Maan2015-08-191-1/+1
|
* Make sure Sidekiq picks up archive_repo queue in production.repository-archive-workerDouwe Maan2015-04-011-1/+1
|
* Revert "Delete mailer queue"Marin Jankovski2014-09-101-1/+1
|
* Wrap arguments for `[ -z` in double quotesJacob Vosmaer2014-09-081-1/+1
|
* Merge pull request #7258 from presto53/fix_init_scripts_interpreterJacob Vosmaer2014-09-081-9/+9
|\ | | | | change bash to sh in web, background_jobs scripts
| * fix bash-ismPavel Novitskiy2014-07-041-1/+1
| |
| * change bash to shPavel Novitskiy2014-07-041-8/+8
| |
* | Delete mailer queue because we don't use sidekiq_mailer gem and now the ↵ling.su2014-07-041-1/+1
|/ | | | mailer queue doesn't exist any more.
* Be more selective when killing stray SidekiqsJacob Vosmaer2014-06-121-1/+1
| | | | | | 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'.
* Move from script to bin directory.Marin Jankovski2014-05-271-0/+80
View Lorry Controller Status