Skip to content
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 backend: Switch from Redis to Django DB #3250

Closed
rtibbles opened this issue Aug 3, 2021 · 0 comments · Fixed by #3332
Closed

Celery backend: Switch from Redis to Django DB #3250

rtibbles opened this issue Aug 3, 2021 · 0 comments · Fixed by #3332

Comments

@rtibbles
Copy link
Member

rtibbles commented Aug 3, 2021

Observed behavior

We currently use a Task Model to track tasks - however, because our actual Celery backend is in Redis, it is possible for these two systems to get out of sync and to give false or misleading information to users and the rest of the system.

Expected behavior

The Task model should accurately represent the state of the task.

The easiest way to do that seems to be to use the Task model as the backend for Celery.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment