This repository was archived by the owner on Aug 26, 2022. It is now read-only.
bug 1268257: Results backend from env, use redis#4615
Merged
Conversation
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.
escattone
approved these changes
Jan 4, 2018
escattone
left a comment
Contributor
There was a problem hiding this comment.
This is a great idea, and a good first step towards using it in production. Thanks @jwhitlock!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Set the
CELERY_RESULTS_BACKENDfrom 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.