-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Celery compatibility issue #213
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using django-multitenant together with Celery and a Redis broker.
I've added a tenant_id parameter to all my celery functions. When the tasks start it calls 'set_current_tenant' with this tenant ID.
In one case I forgot to call 'set_current_tenant', however, it used the tenant_id of the task that was last ran. It is as if it remembered the tenant_id of another task that another user (of another tenant) ran.
I thought that this shouldn't be possible, so I'm worried about potential unintended consequences this may have, such as race conditions.
Is this project compatible with Celery and if so, is there any particular configuration I should do?
The text was updated successfully, but these errors were encountered: