Closed Bug 1268257 Opened 8 years ago Closed 6 years ago

Switch away from the Django database as a celery results backend

Categories

(developer.mozilla.org Graveyard :: Code Cleanup, enhancement)

All
Other
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jwhitlock, Unassigned)

References

Details

(Whiteboard: [specification][type:feature])

What problem would this feature solve?
======================================
Currently, async task results are stored in the Django database, using the package django-celery, which is deprecated

Who has this problem?
=====================
Code Maintainers

How do you know that the users identified above have this problem?
==================================================================
django-celery is deprecated and may break in future versions of Django.

How are the users identified above solving this problem now?
============================================================
The async task results are stored in the Django database.

Do you have any suggestions for solving the problem? Please explain in detail.
==============================================================================
Configure Redis as a results store, and use the native Redis results store instead of the database store

Is there anything else we should know?
======================================
Due to the stability of the current celery setup in SCL3, I do not recommend doing this work before moving MDN to AWS.
Blocks: 1268254
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/15c9b50d13fb710848b786ace121c1f4272919f7
bug 1268257: Results backend from env, use redis

Set the CELERY_RESULTS_BACKEND from the environment, and use Redis
DB 1 (namespacing feature to distinguish from DB 0 for task queues)
instead of the Django database in development. A similar change is
planned in production to reduce database usage.

https://github.com/mozilla/kuma/commit/1af66341850ad422d6c533e3270e4904926881aa
Merge pull request #4615 from jwhitlock/celery-results-1268257

bug 1268257: Results backend from env, use redis
This shipped three months ago. I didn't close it because tasks results are still being sent to Django. However, this appears to be due to the "celerymon" service. Deprecation of that feature is part of bug 1268281.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.