DGNum/demarches-normaliennes
13
1
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity

BREAKING(sidekiq.queues): rationalize queues. now have critical, default, low

Browse source 
Dear instances, make sure to update your sidekiq processes. Indead, we are adopting a new strategy for daemons that process our background
jobs.

Now their is only 3 queues on sidekiq (still, we keep archive/export on delayed job for now).

The big idea : allow any worker to deal with any queue (capacity mgmt) :
- critical: must be procesed now
- default: will be processed asap
- low: do it after everything else

FYI: we had 50% of our server capacity on reserved queues. Leading to
bottle neck processing (reserved queues/worker not processing other
queues). We HAD TO fix it. Sorry for the inconvenience

TBH, this is an idea of Colin Darie <colin@darie.eu>. I'm just pushing
it forward.

Co-Authored-By: Colin Darie <colin@darie.eu>
This commit is contained in:
mfo 2024-09-24 20:58:26 +02:00
parent 0cbb296e7d
commit 08ec45443d
No known key found for this signature in database
GPG key ID: 7CE3E1F5B794A8EC
9 changed files with 8 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

2
app/jobs/dossier_rebase_job.rb
View file

@ -1,7 +1,7 @@
# frozen_string_literal: true
class DossierRebaseJob < ApplicationJob
queue_as :low_priority # they are massively enqueued, so don't interfere with others especially antivirus
queue_as :low # they are massively enqueued, so don't interfere with others especially antivirus
# If by the time the job runs the Dossier has been deleted, ignore the rebase
discard_on ActiveRecord::RecordNotFound