Contributors mailing list archives
contributors@odoo-community.org
Browse archives
ERROR: could not serialize access due to concurrent update (case using Job Queue)
by
Ecosoft Co. Ltd., Kitti Upariphutthiphong
Dear community,
We have a case that needs to process a lot of transactions (500k arrive on the last day of month). And so we rely on our best friend OCA's Job Queue and have things run in parallel.
Most process are OK, but the one creates stock picking, jobs can't run in parallel because there is a concurrent issue on the "stock_quant" table, which looks like many separated job is updating the same record.
bad query: update stock_quant set reserved_quantity = 10.00 ... where id in (100)
ERROR: could not serialize access due to concurrent update
bad query: update stock_quant set reserved_quantity = 10.00 ... where id in (100)
ERROR: could not serialize access due to concurrent update
.....
Concurrent updates are very common issues we always face. How do you get around with this problem?
Thank you,
Kitti U.
Follow-Ups
-
Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)
byEcosoft Co. Ltd., Kitti Upariphutthiphong -
Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)
byTecnativa. S. L., Pedro M. Baeza -
Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)
byTherp, Tom Blauwendraat -
Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)
byAkretion France., Florian da Costa -
Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)
byEcosoft Co. Ltd., Kitti Upariphutthiphong -
Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)
by "Adam Heinz" <adam.heinz@metricwise.com> - 04/03/2024 14:31:20 - 0