Commit graph

11 commits

Author SHA1 Message Date
Douwe Maan
0b15570e49 Add ApplicationWorker and make every worker include it 2017-12-05 11:59:39 +01:00
Micael Bergeron
45c373caf5 [ci-skip] linting 2017-11-14 18:12:52 +00:00
micael.bergeron
0b4a7d656b rework the logging to be simpler and add a threshold 2017-11-14 09:22:15 -05:00
micael.bergeron
bae6385bda add simple logging to UpdateMergeRequestsWorker#perform
this is to try to debug #35914
2017-11-13 14:56:08 -05:00
micael.bergeron
7fd3ce417f Revert "add metrics tagging to the sidekiq middleware"
This reverts commit d5859bb9d5.
This reverts commit 2b7e03cf69.
This reverts commit 7799a9bc44.
2017-11-08 16:21:08 -05:00
micael.bergeron
d5859bb9d5 rework the UpdateMergeRequestsWorker#metrics_tags 2017-11-01 09:07:27 -04:00
micael.bergeron
2b7e03cf69 reword targets to metric tags
add changelog
2017-10-31 13:21:08 -04:00
micael.bergeron
7799a9bc44 add metrics tagging to the sidekiq middleware 2017-10-31 09:48:10 -04:00
gpongelli
4bcd900f14 Moved call of SystemHooksService from UpdateMergeRequestsWorker to GitPushServic… 2017-03-07 12:59:20 +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
Paco Guzman
bba4788626 Extract project#update_merge_requests and SystemHooks to its own worker from GitPushService 2016-10-13 17:23:24 +02:00