-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Magento 2.3.1 Cron Deadlocks for cron_schedule #22438
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @seansan. Thank you for your report.
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:
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?
|
Hi @engcom-backlog-nazar. Thank you for working on this issue.
|
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>
.
|
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 |
I have some sites in 2.2.6 and look like same issue :( |
Same issue here on 2.2.8. |
Same problem here with 2.3.1. We import data with an API and I suspect that the cron interferes with my hourly syncs. |
Also experiencing issue on 2.3.1 with specific deadlocks occurring on the cron_schedule table |
Have the same issue. Thought 2.3 will be better than any 1.X version . Made the switch and spend hours making it ready with all prerequisites . The symptoms is if you enable crontab and few crons are run, looks like and overlapp happens and it brings the cpu to 99% . The top on Centos 6 shows PHP and PHPFPM causing this. Eventually found crons are stuck. I saw a possible solution with https://github.com/magemojo/m2-ce-cron . Has anyone tried this. |
Hi @engcom-Charlie. Thank you for working on this issue.
|
✅ Confirmed by @engcom-Charlie Issue Available: @engcom-Charlie, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself. |
@engcom-Charlie: since you were able to reproduce this problem, could you also add the exact steps of how to do this? Since that info doesn't seem to be in this issue yet. That would be very much appreciated, thanks! |
@hostep I have the same problem as @manish3m #22438 (comment). Maybe I made a mistake when i confirmed this issue. |
@hostep Steps to reproduce :
Actual result: |
Quite confusing!!! |
Yes indeed, very confusing. @engcom-Charlie on what Magento version did you first test it when you were able to reproduce it? This wasn't on the |
@hostep yes, but i had no deadlocks.Sorry but when i confirmed this issue i reproduced the problem that is described in the #22438 (comment) . |
@engcom-Charlie maybe they has relation and high CPU can cause deadlock. If so do we have a fix/MR for high CPU? |
@onlinebizsoft |
@engcom-Charlie so there is a bug. Did you fix this CPU issue? |
@onlinebizsoft it is not fixed yet. Please create a new issue for this bug. I can't confirm this issue because it's about deadlocks. |
Same issue on 2.3.3, here is the log :
Vanilla 2.3.3 install. Ubuntu 18.04, PHP 7.3 |
Still happens 2.3.3 |
|
Hi @seansan. Thank you for your report.
The fix will be available with the upcoming 2.4.3 release. |
Still an issue in Magento 2.4.7-p5. What a joke. |
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)
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
The text was updated successfully, but these errors were encountered: