multiple consumers -> Deadlock found when trying to get lock

Hello,

ORO Platform version: 2.6.31

When I have more than one instance of consumers running by supervisor:

[program:platform_message_consumer] command=php /home/oropl/public_html/app/console oro:message-queue:consume --env=prod process_name=%(program_name)s_%(process_num)02d numprocs=4 autostart=true autorestart=true startsecs=0 user=root redirect_stderr=true

1 2 3 4 5 6 7 8 9

[program:platform_message_consumer] command=php /home/oropl/public_html/app/console oro:message-queue:consume --env=prod process_name=%(program_name)s_%(process_num)02d numprocs=4 autostart=true autorestart=true startsecs=0 user=root redirect_stderr=true

I get lots of these errors:

An exception occurred while executing ‘DELETE FROM oro_message_queue WHERE id=:messageId LIMIT 1’ with params [\”2541\”]:\n\nSQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction at /home/oropl/public_html/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractMySQLDriver.php:115

An error occurred while running command “‘oro:message-queue:consume’ –env=prod”. An exception occurred while executing ‘DELETE FROM oro_message_queue WHERE id=:messageId LIMIT 1’ with params [“2541”]: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction {“exit_code”:0,”exception”:”[object] (Doctrine\\DBAL\\Exception\\DriverException(code: 0)

When I change it to only one instance of consumer problem is resolved.

Is this an issue?

Thanks

Topic

[Andrey YatsenkoModerator]

Deadlock in MQ could be OK in some rear cases, the message should be redelivered with some delay and will be processed next time without locks.
If you have deadlocks all the time, probably it’s a bug. In that case, please share a number of records, consumer working on and what messages are in progress.

Thank you.

[Author]

Replies