Closed lfse-slafleur closed 2 months ago
Did some investigating:
delivery-limit
with classic queues and requires us to move to quorum queues
.priorities
so we will be giving up support from RabbitMQ with this move (https://www.rabbitmq.com/docs/quorum-queues#feature-matrix). While message priorities may become important later, currently no support for prioritisation is required.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.
- Celery does not support quorum queue's out of the box but official support is incoming: support for quorum queues celery/celery#6067
On it’s way: https://github.com/celery/celery/pull/9121
Also, per the topic of this issue, see: https://www.rabbitmq.com/docs/migrate-mcq-to-qq
- Celery does not support quorum queue's out of the box but official support is incoming: support for quorum queues celery/celery#6067
On it’s way: celery/celery#9121
@Nusnus Thank you Tomer for the references and for adding this to Celery, much appreciated!
Support for Quorum queues is available in Celery main release available soon. Switching over to component tickets for tracking and closing this one.
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
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!