Skip to content

[WPB-28375] Move sync-user-group background jobs from RabbitMQ to Arbiter - #5490

Open
blackheaven wants to merge 1 commit into
developfrom
gdifolco/WPB-28375-background-jobs-arbiter
Open

[WPB-28375] Move sync-user-group background jobs from RabbitMQ to Arbiter#5490
blackheaven wants to merge 1 commit into
developfrom
gdifolco/WPB-28375-background-jobs-arbiter

Conversation

@blackheaven

Copy link
Copy Markdown
Contributor

https://wearezeta.atlassian.net/browse/WPB-28375

Checklist

  • Add a new entry in an appropriate subdirectory of changelog.d
  • Read and follow the PR guidelines

@blackheaven
blackheaven requested review from a team as code owners August 28, 2026 08:53
@zebot zebot added the ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist label Aug 28, 2026
@blackheaven
blackheaven force-pushed the gdifolco/WPB-28375-background-jobs-arbiter branch from 6ac3844 to 159cd2b Compare August 28, 2026 08:57
…iter

Add a 'user-groups' queue to the Arbiter job registry with a
UserGroupsJobPayload sum (sync_user_group / sync_user_group_and_channel).
brig now publishes sync jobs through the shared Postgres pool (per-group
serialization, 3 attempts) and runs the registry migrations at startup.
background-worker consumes the queue in a third Arbiter worker pool,
reusing the existing dispatch pipeline; chained syncs are published back
onto Arbiter and failures are retried via throwRetryable.

The RabbitMQ jobs path is removed: jobs consumer and registry modules,
RabbitMQ publisher interpreter, the BackgroundJob envelope and its dead
serialization, the amqpJobsPublisherChannel in brig and background-worker,
the backgroundJobs config block, and the corresponding charts, docs, and
queue assertions in Test.Events. Backend-notification push and
dead-user-notification watching remain on RabbitMQ.
@blackheaven
blackheaven force-pushed the gdifolco/WPB-28375-background-jobs-arbiter branch from 159cd2b to 377e193 Compare August 28, 2026 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants