-
-
Notifications
You must be signed in to change notification settings - Fork 460
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
[Question] queue_job when multiple odoo servers are used with load balancing (and single postgres) #422
Comments
@JordiBForgeFlow you need to make sure that only one Odoo instance has Alternatively, you can launch a separate job runner process with something like #409. |
See also #256 |
There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
@sbidoul having to tweak the configuration for one instance can become an issue when we have to deploy to a variable number of Odoo instances. Is it not possible to namescope the NOTIFY payload with host/main-odoo-pid/dbname to allow multiple job-runners to be active? |
@daemonblade in such situations, I don't add queue_job to server_wide_modules, and instead start the job runner independently, so all Odoo instances can share the same config. Multiple job runners is tricky because it is currently all based on the queue being in memory. |
Hi @sbidoul how can I run the queue_job independently? I've tried this
|
Try You'll need to add |
I've reviewed our logs for multi-node systems with queue_job. We have one instance configured with queue_job in |
In the scenario where multiple odoo servers are used with load balancing, and a single postgres server is used, will all of the odoo servers try to run all the jobs?
The text was updated successfully, but these errors were encountered: