Repository navigation
[Feature] Concurrent job runners #2
Description
In a use case with several hosts running Odoo, we might want either to:
- allow several jobrunners to run concurrently on several hosts, which might be hard due to the queues kept in local memory
- elect a master jobrunner allowing to work, the other ones wait and one of them takes over if the master is down
Activity
lasley commentedon Nov 4, 2016
IMO the best way to implement this would be a Message Broker, such as RabbitMQ.
We would just need to advertise to and ingest from a simple Work queue. In the event of the master down, an Alternate Exchange would do nicely I think.
Merge pull request #2 from acsone/10.0-queue-job-ape
yucer commentedon Mar 16, 2017
Odoo optionally uses gevent for the bus. So the dependency is already there.
Maybe gevent.queue can be used with that purpose.
thomaspaulb commentedon Sep 7, 2021
Elect a master jobrunner allowing to work, the other ones wait and one of them takes over if the master is down
Could this be done via a database lock? Eg. each Odoo instance regularly tries to grab a database lock by which to become the master job runner; if it succeeds, it becomes, if not, does nothing and tries again after a while.
thomaspaulb commentedon Sep 7, 2021
Something like this:
https://github.com/OCA/OCB/blob/11.0/odoo/addons/base/ir/ir_cron.py#L209
nilshamerlinck commentedon Sep 7, 2021
Hi @thomaspaulb you might want to have a look at #256 :)
thomaspaulb commentedon Sep 7, 2021
@nilshamerlinck I actually just found that one too haha, thanks.
github-actions commentedon Mar 6, 2022
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.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.