MySQL deadlock transactions in oro:message-queue:consume

I have a many deadlock transactions while oro:message-queue:consume working and its overload mysql server.
Why its happens and how i can fix it?

Topic

[Andrew FetisovModerator]

Hi, swaroge!
Could you please tell me which version of OroCRM and DB you are using?
The described error message is, unfortunately, not enough to understand what is wrong. Could you please show me a more detailed error of oro:message-queue:consume with max verbosity level and steps to reproduce your problem? Thanks

[swarogeParticipant]

Im using the 2.3.0 version
You can see full log of mysql innoDB status here https://drive.google.com/open?id=1k0xld3oopc7lAVcSj_-93DUYut7TPz1t

[Andrew FetisovModerator]

I’ve looked at your log, according to it – the problem could be in oro:cron:imap-sync command.
But in order to reproduce your issue, we still need more detailed info about your issue.
I suggest to recheck your DB settings:
https://oroinc.com/doc/orocrm/2.0/system-requirements
IMAP settings (if it related to imap sync):
https://oroinc.com/doc/orocrm/2.0/admin-guide/email/email-configuration

In order to try to isolate this issue please make clean install ORO application from scratch and configure your test/work IMAP account again.
Manually run app/console oro:cron:imap-sync and run consumer with -vvv option.

How many consumers did you run? It could be “race condition” problem, try to run the only ONE consumer

[swarogeParticipant]

Thx. I have good configs for imap and for the DB. I think “In order to try to isolate this issue please make clean install ORO application from scratch ” will help.
About the Consumer – i have 4 consumers running via supervisor.

[swarogeParticipant]

Problem solved. I was reinstall crm.

[Author]

Replies