fix: add CELERY_RESULT_BACKEND with default django-cache#6722
Conversation
|
Thanks for the pull request, @navinkarkera! I've created OSPR-6623 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR. Feel free to add as much of the following information to the ticket as you can:
All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here. Please let us know once your PR is ready for our review and all tests are green. |
|
@navinkarkera Thank you for your contribution. Please let me know once it is ready for our review. |
|
@navinkarkera Just checking if this is ready for our review, please let me know. |
|
👍 Looks good to go from my end.
|
|
@natabene This is ready for your review. |
|
@navinkarkera Thanks! @BbrSofiane This is ready for your review. |
21e99c8 to
ce9701e
Compare
|
Thanks @natabene, Just updated the commit message to fix commit lint error. |
|
@navinkarkera 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
Configuration Pull Request
Cherry pick of #6720
Note: This PR has a corresponding edx-platform PR openedx/openedx-platform#30246
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"