1. Mailing Lists
  2. Contributors
  3. Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)

Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)

Avatar

Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)

by
Akretion France., Florian da Costa
- 04/03/2024 15:13:55
Hello,

Your problem seems to be linked to stock reservation. By default, picking types (Operation types) are configured to make the stock reservation at picking confirmation. If this is the case, these concurrent update errors are not surprising if the created pickings contain the same product.
You could try to change the "Reservation Method" on the concerned picking type(s) to "manual". And then manage the stock reservation on picking one by one afterward.

Regards,
Florian

Le lun. 4 mars 2024 à 15:07, Kitti Upariphutthiphong <notifications@odoo-community.org> a écrit :
Thanks Adam,

In fact, if we don't have time constraints, it will work.

The problem is we really need to have many job (like 10 processes that create picking) to run simultaneously and without locking in order to achieve 500k records (more in the future) in very limit time (couple hours).

I was thinking if there are anyway to unlock the table at least temporarily during execution. But as far as I researching, I still can't find the way yet.

On Mon, Mar 4, 2024 at 8:37 PM Adam Heinz <notifications@odoo-community.org> wrote:
I have a couple of strategies that I use, neither of which I am in love with:

1. Catch the serialization error and reraise a RetryableJobError. This works well enough when serialization errors are intermittent and the job has no side-effects.
2. Set ODOO_QUEUE_JOB_CHANNELS=root:32,single:1 in the environment, and put problematic jobs into the `single` channel. This is a tool of last resort as it slows problematic jobs down to single threaded, but I have found it necessary when the serialization errors occur on basically every execution.

On Mon, Mar 4, 2024 at 8:17 AM Kitti Upariphutthiphong <notifications@odoo-community.org> wrote:
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.








_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

Reference