-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: allow to run multiple celery queues and workers #1
Conversation
0c34ee1
to
ad0a4b0
Compare
@Ian2012 I remain attentive to the results of the tests adding LMS tasks to CMS configuration (via EXPLICIT_QUEUES) and vice-versa |
@jfavellar90 Mixing the settings for the tasks routes can cause different issues, I've decided to create two separate variables to control LMS and CMS workers tasks routing. |
README.md
Outdated
- cms_custom_queue | ||
``` | ||
|
||
This plugin also provides a setting to directly route LMS/CMS tasks to an specific queue: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's important to mention that this will extend/override the variable EXPLICIT_QUEUES
on both LMS and CMS
I already provided my approval @Ian2012, however, please fix the minor detail I mentioned in my last comment and proceed with the merge. |
Description
This PR allows the deployment of multiple celery queues and workers via settings. It also overrides the default lms-worker deployment to prevent it to consume events from all queues.
Deployed on
musashi/tunis
Future work
gevent
pool (installgevent
on openedx via this plugin)