Project-OMOTES / architecture-documentation

0 stars 0 forks source link

Migrate to Quorum queues in rabbitmq and setup message poisoning & deadletter queues #25

Closed lfse-slafleur closed 2 months ago

lfse-slafleur commented 5 months ago
lfse-slafleur commented 3 months ago

Did some investigating:

lfse-slafleur commented 3 months ago

Decided that delivery-limit functionality is required currently to solve the issue of having a job be retrieved definitely when it causes an OOM.

Prioritization is still important as well because we need a mechanism to combat having a single user fill up the queues with large amounts of jobs and not being able to have another user's job overtake the existing jobs.

Nusnus commented 2 months ago

On it’s way: https://github.com/celery/celery/pull/9121

Nusnus commented 2 months ago

Also, per the topic of this issue, see: https://www.rabbitmq.com/docs/migrate-mcq-to-qq

lfse-slafleur commented 2 months ago

On it’s way: celery/celery#9121

@Nusnus Thank you Tomer for the references and for adding this to Celery, much appreciated!

lfse-slafleur commented 2 months ago

Support for Quorum queues is available in Celery main release available soon. Switching over to component tickets for tracking and closing this one.

Nusnus commented 2 months ago

Support for Quorum queues is available in Celery main release available soon. Switching over to component tickets for tracking and closing this one.

Celery v5.5.0b1 was released with the new feature support.

@lfse-slafleur

lfse-slafleur commented 2 months ago

Support for Quorum queues is available in Celery main release available soon. Switching over to component tickets for tracking and closing this one.

Celery v5.5.0b1 was released with the new feature support.

@lfse-slafleur

@Nusnus Thanks again Tomer! Great work!