Magento 2.3.1 Cron Deadlocks for cron_schedule

[seansan]

Preconditions (*)

1. Magento 2.3.1
2. MSI

Steps to reproduce (*)

1. Vanilla install
2. Run CRON every 1 minutes 3 jobs main, setup and upgrade

Expected result (*)

1. No CRON problems, especially no deadlocks for a simple table .... truncating the table only works 1time ... need a structural solution or some kind of retry method

Actual result (*)

1. See below

This really should not happen

https://magento.stackexchange.com/questions/270856/magento-2-v2-3-1-cron-causing-intermittent-deadlock-for-cron-schedule

https://magento.stackexchange.com/questions/238454/cron-job-error-sqlstate40001-serialization-failure-1213-deadlock-found-when?rq=1

https://magento.stackexchange.com/questions/203107/magento-2-cron-schedule-table-increasing-and-cpu-100

https://magento.stackexchange.com/questions/270813/magento-2-3-1-vanilla-cron-error-serialization-failure-1213-deadlock-found-whe

[m2-assistant]

Hi @seansan. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@seansan do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[m2-assistant]

Hi @engcom-backlog-nazar. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

HI @seansan thank you for you report, i'm closing this as duplicate to this -> #8933

[seansan]

that is a very very old issue almost 2 years, especially in the code world can something be done to solve this issue you think

…

On Mon, Apr 22, 2019 at 9:45 AM engcom-backlog-nazar < ***@***.***> wrote: Closed #22438 <#22438>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#22438 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAE7I245SV6UXYMDPCQSJJ3PRVUIHANCNFSM4HHKD3PQ> .

[seansan]

Please re=open this issue. the other issue may be about a deadlock but the case is completely different it is about INDEXER and only accurs occasionaly

This is about a very specific CRON schedule

And can influence ALL users that use cron

[onlinebizsoft]

I have some sites in 2.2.6 and look like same issue :(

[Ctucker9233]

Same issue here on 2.2.8.

[lracicot]

Same problem here with 2.3.1. We import data with an API and I suspect that the cron interferes with my hourly syncs.

[driskell]

Also experiencing issue on 2.3.1 with specific deadlocks occurring on the cron_schedule table