8 Commits

Author	SHA1	Message	Date
Stan Hu	b33661d6ec	Add ExclusiveLease guards for RepositoryCheck::{DispatchWorker,BatchWorker} ... We saw in production that DispatchWorker was running about twice an hour, which would schedule twice as many jobs as it should. For some reason, BatchWorker was running 1000 times per hour, possibly due to Sidekiq RSS kills that caused these jobs to restart. Adding an ExclusiveLease prevents these jobs from running more than they should. Relates to https://gitlab.com/gitlab-com/infrastructure/issues/4526	2018-07-06 10:11:59 -07:00
Toon Claes	95ac8b0e1d	Add RepositoryCheck::DispatchWorker to start worker per shard ... The RepositoryCheck::DispatchWorker will start a RepositoryCheck::BatchWorker for each healthy shard. Closes gitlab-org/gitlab-ce#48042	2018-06-27 21:43:23 +02:00
Toon Claes	b07c4e3dc4	Remove `Rails.env.test?` from production code	2018-05-07 09:42:09 +02:00
Robert Speicher	72a7b30c9f	Change all `:empty_project` to `:project`	2017-08-02 17:47:31 -04:00
Robert Speicher	68e6718932	Use `:empty_project` where possible in worker specs	2017-03-27 18:45:37 -04:00
Jacob Vosmaer	3c0ab15a74	Do not fsck projects less than a day old ... This should bring the number of false positives down.	2016-04-26 13:35:52 +02:00
Jacob Vosmaer	6f6d2d0ad5	Use more conservative limits	2016-04-13 17:33:25 +02:00
Jacob Vosmaer	0f602be99f	Clear repository check columns asynchronously	2016-04-13 15:56:05 +02:00