This repository was archived by the owner on Aug 3, 2026. It is now read-only.
fix: add CELERY_RESULT_BACKEND with default django-cache - #191
Merged
navinkarkera merged 2 commits intoMay 26, 2022
Merged
Conversation
Member
|
👍 Looks good to go from my end.
|
farhaanbukhsh
pushed a commit
that referenced
this pull request
Jun 16, 2022
* fix: add CELERY_RESULT_BACKEND with default django-cache * Update CHANGELOG.md
0x29a
pushed a commit
that referenced
this pull request
Jun 17, 2022
* fix: add CELERY_RESULT_BACKEND with default django-cache * Update CHANGELOG.md
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.
Configuration Pull Request
Cherry pick of openedx-unsupported#6720
Note: This PR has a corresponding edx-platform PR open-craft/openedx-platform#467
Description
At Opencraft, we want to run multiple instances of celery workers in separate servers. The celery workers need to be able to share task results. Currently, the
CELERY_RESULT_BACKENDis hard coded to usedjango-cache.So this PR allows to setup
CELERY_RESULT_BACKENDvia configuration.To use django ORM as celery backend, one can set
CELERY_RESULT_BACKENDtodjango-dbas described in docs.Supporting information
Deadline
"None"