Commit graph

8 commits

Author SHA1 Message Date
Dylan Griffith
bbcc18080b Update sidekiq_style_guide.md 2018-02-13 05:10:04 +00:00
Dylan Griffith
e8648270af Document all_queues.yml in sidekiq_style_guide.md 2018-02-13 16:08:02 +11:00
Douwe Maan
0ec81dd5ac Update docs 2017-12-12 17:36:20 +01:00
Douwe Maan
a5c3f1c8ff Update docs 2017-12-05 11:59:39 +01:00
Douwe Maan
0b15570e49 Add ApplicationWorker and make every worker include it 2017-12-05 11:59:39 +01:00
Dmitriy Zaporozhets
921e5ab0e1 Capitalize Sidekiq word in dev doc 2017-07-21 17:40:48 +00:00
Dmitriy Zaporozhets
5d90de1cb2 Update sidekiq_style_guide.md with removing or renaming queues instructions 2017-07-21 07:20:35 +00:00
Yorick Peterse
97731760d7
Re-organize queues to use for Sidekiq
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
2016-10-21 18:17:07 +02:00