kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/app/workers/git_garbage_collect_worker.rb

20 lines
720 B
Ruby
Raw Normal View History

Enable frozen string literals for app/workers/*.rb
2018-06-27 03:23:28 -04:00
# frozen_string_literal: true
Add latest changes from gitlab-org/gitlab@master
2021-01-21 07:09:05 -05:00
# According to our docs, we can only remove workers on major releases
# https://docs.gitlab.com/ee/development/sidekiq_style_guide.html#removing-workers.
#
# We need to still maintain this until 14.0 but with the current functionality.
#
# In https://gitlab.com/gitlab-org/gitlab/-/issues/299290 we track that removal.
Add latest changes from gitlab-org/gitlab@master
2020-02-19 13:09:10 -05:00
class GitGarbageCollectWorker # rubocop:disable Scalability/IdempotentWorker
Add ApplicationWorker and make every worker include it
2017-11-28 11:08:30 -05:00
include ApplicationWorker
Expire the branch cache after `git gc` runs Due to a stale NFS cache, it's possible that a branch lookup fails while `git gc` is running and causes missing branches in merge requests. Possible workaround for #15392
2016-07-08 15:32:58 -04:00
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 12:13:41 -04:00
sidekiq_options retry: false
Add latest changes from gitlab-org/gitlab@master
2019-10-18 07:11:44 -04:00
feature_category :gitaly
Add latest changes from gitlab-org/gitlab@master
2020-06-12 08:08:56 -04:00
loggable_arguments 1, 2, 3
Expire the branch cache after `git gc` runs Due to a stale NFS cache, it's possible that a branch lookup fails while `git gc` is running and causes missing branches in merge requests. Possible workaround for #15392
2016-07-08 15:32:58 -04:00
Refine Git garbage collection
2016-10-27 08:59:52 -04:00
def perform(project_id, task = :gc, lease_key = nil, lease_uuid = nil)
Add latest changes from gitlab-org/gitlab@master
2021-01-21 07:09:05 -05:00
::Projects::GitGarbageCollectWorker.new.perform(project_id, task, lease_key, lease_uuid)
Refine Git garbage collection
2016-10-27 08:59:52 -04:00
end
Expire the branch cache after `git gc` runs Due to a stale NFS cache, it's possible that a branch lookup fails while `git gc` is running and causes missing branches in merge requests. Possible workaround for #15392
2016-07-08 15:32:58 -04:00
end
Copy permalink