Multiple Celery projects on same Redis database #7152
Replies: 3 comments 2 replies
-
|
Could we have an update on this ? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
From my (limited) experience with the code of the kombu redis transport, I would expect that the queue bindings will not work as expected, and if one service accidentally tries to restore an unacked message from another service, you might just lose your tasks. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I have a question regarding Celery. We have a software system in which there are several services that use Celery using the same Redis instance as a broker.
In addition to that, we're sharing the same DB of celery for each installation and we've different versions of Celery/kombu for each service (different versions of Celery 4.X/ Kombu 4.X). The segregation that we are using is based on the queue names.
I saw that Kombu uses the same data structures to track the unacked messages that are not segregated by queue/project and so I'm afraid that can cause collisions/unexpected behaviours of Celery.
Is this considered a safe approach? Does Celery support this kind of approach?
Any advice is really appreciated!
Thanks,
Simone
Beta Was this translation helpful? Give feedback.
All reactions