-
-
Notifications
You must be signed in to change notification settings - Fork 467
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
[RFC] jobrunner cli #409
[RFC] jobrunner cli #409
Conversation
With this, there is no need for queue_job in server_wide_modules. |
ef61552
to
f415ec6
Compare
This seems to work well in our first tests. I think we can merge this as it is non-intrusive. I'll document it when we have more experience in production. |
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.
Very good indeed for k8s-style infrastructure. Thanks!
We've run full loop with the old odoo-job-runner start script (don't remember the exact name) 😆
/ocabot merge patch |
On my way to merge this fine PR! |
Congratulations, your PR was merged at dab2bcb. Thanks a lot for contributing to OCA. ❤️ |
/!\ This is very rough and mostly untested. So just an idea so far.I wonder if running the job runner in a standalone process could be a solution to the problem of running a single job runner in a multi-node deployment.
We could then let the responsibility of running one replica of the job runner to the orchestrator (say, k8s), and we don't need ensure it's a singleton ourselves.
Use with
env ODOO_RC=odoo.cfg python -m odoo.addons.queue_job.jobrunner
.