Browse Source

Change incoming activity processing to happen in `ingress` queue (#20264)

closed-social-glitch-2
Eugen Rochko 2 years ago
committed by GitHub
parent
commit
f8e8e622e5
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 5 additions and 3 deletions
  1. +1
    -0
      app/lib/admin/system_check/sidekiq_process_check.rb
  2. +1
    -1
      app/workers/activitypub/processing_worker.rb
  3. +3
    -2
      config/sidekiq.yml

+ 1
- 0
app/lib/admin/system_check/sidekiq_process_check.rb View File

@ -7,6 +7,7 @@ class Admin::SystemCheck::SidekiqProcessCheck < Admin::SystemCheck::BaseCheck
mailers
pull
scheduler
ingress
).freeze
def skip?

+ 1
- 1
app/workers/activitypub/processing_worker.rb View File

@ -3,7 +3,7 @@
class ActivityPub::ProcessingWorker
include Sidekiq::Worker
sidekiq_options backtrace: true, retry: 8
sidekiq_options queue: 'ingress', backtrace: true, retry: 8
def perform(actor_id, body, delivered_to_account_id = nil, actor_type = 'Account')
case actor_type

+ 3
- 2
config/sidekiq.yml View File

@ -1,8 +1,9 @@
---
:concurrency: 5
:queues:
- [default, 6]
- [push, 4]
- [default, 8]
- [push, 6]
- [ingress, 4]
- [mailers, 2]
- [pull]
- [scheduler]

Loading…
Cancel
Save