Cronjobs increasing CPU usage and slow queries

[Zyles]

Cronjobs stuck in pending state. CPU usage increasing. Mysql slow queries increasing.

Time is 13:28.

Logs filled with:

use magento;
SET timestamp=1579781526;
SELECT GET_LOCK('|CRON_GROUP_default', '5');
# Time: 200123 13:13:06
# User@Host: magento[magento] @ localhost []
# Thread_id: 20330  Schema: magento  QC_hit: No
# Query_time: 2.951003  Lock_time: 0.000000  Rows_sent: 1  Rows_examined: 0
# Rows_affected: 0
SET timestamp=1579781586;

Load goes down after disabling cronjob in crontab:

Preconditions (*)

Magento 2.3.3 & 2.4-develop
PHP-FPM 7.2.24

Steps to reproduce (*)

1. Install Magento
2. Setup cron jobs
3. Run store for a week
4. Break store

Expected result (*)

Normal working store.

Actual result (*)

1. Increased CPU usage
2. Increased cronjobs count
3. Increased slow queries
4. Slow store

[m2-assistant]

Hi @Zyles. 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 give me 2.4-develop instance - upcoming 2.4.x release

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

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

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[gwharton]

Do ypu have any jobs stuck "running"

[devchris79]

We see some cron jobs stuck in the running status:

That's with a Magento 2.3.3 installation.

[gwharton]

If you manually delete the rows that are stuck running, the pending jobs should be cleaned back to normal levels over the next few cron runs.

[gwharton]

But you need to look at why they do not complete. It would be better if magento had some timeout to terminate stuck running jobs.

[devchris79]

I have deleted them out before, but they returned (as I suppose you would expect). I will try again and try to understand the sticking.

I agree with the timeout to terminate stuck routines, that would be great. I also don't understand why we have routines stuck in the "running" state with no execution time stamp, surely that should be the first thing done....

[Zyles]

Didn't check "running". Truncated table as it took up too much server resources.

Clearly a bug.

One should not routinely have to empty the table manually.

[m2-assistant]

Hi @engcom-Hotel. 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.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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. Add label Issue: Confirmed once verification is complete.

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

[magento-engcom-team]

✅ Confirmed by @engcom-Hotel
Thank you for verifying the issue. Based on the provided information internal tickets MC-30804 were created

Issue Available: @engcom-Hotel, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[devchris79]

I have tweaked my cron job setup slightly and so far there hasn't been any sticking in the running state. I am wondering if its possible that two or more instances of the same cron job are being run at the same time and if that's causing lockup.

[anil90]

hi @devchris79 we are also facing same issue with Magento 2.3.2 Could you please let us know your changes. Thank you

[devchris79]

Hi @anil90 we are still seeing the issues. I think the timing is a red herring.

[devchris79]

The issue #26809 contains a post that highlights the extra ram usage in the cron processes from Magento 2.3.3.

Our site currently has no jobs stuck in the running state for over a day, and I have only made two changes:

1, Truncated the cron log as it was getting very large
2, We were seeing errors in the system log relating to aqmp not being configured. We don't use RabbitMQ so I just added the code below to env.php:

,
'cron_consumers_runner' => [
        'cron_run' => false,
        'max_messages' => 1000,
        'consumers' => [
            'async.operations.all'
        ]
    ] 

[roni-sooryen]

@devchris79 Please keep me up to date with the status of your cron job processes. You can use the https://github.com/kiwicommerce/magento2-cron-scheduler to kill your cron job after the cron job runs for 3 hours.

[devchris79]

@roni-sooryen Happy to report that we still have nothing stuck :-)

[roni-sooryen]

Seems like this is the same issue here #22438

[Zyles]

I've had more success using separate intervals on cronjob, so they do not lock into each other. This is on a medium store.

On a large store the problem should be even more severe since the cronjobs run for longer.

Example:

* * * * * /usr/bin/php /home/http/magento/bin/magento cron:run 2>&1 | grep -v "Ran jobs by schedule" >> /home/http/magento/var/log/magento.cron.log
10 * * * * /usr/bin/php /home/http/magento/update/cron.php >> /home/http/magento/var/log/update.cron.log
15 * * * * /usr/bin/php /home/http/magento/bin/magento setup:cron:run >> /home/http/magento/var/log/setup.cron.log

Also turning off separate processes for each cronjob in backend:

This is by no means a fix, rather a workaround and works for us right now.

[magento-engcom-team]

Hi @Zyles. Thank you for your report.
The issue has been fixed in #28007 by @driskell in 2.4-develop branch
Related commit(s):

• aa12503923ac994873724ecaa759e1eb14b318dc
• b0b72b0f8486ca119015e84b7786dfab13d2e475
• 315bd3af8c5ed3dd711abd40db9a163b0c953855
• 96029b55f7cd00b58967637aedac67ddd1767bad
• 7df183b6c6bc3f57f0c3d29d279c3c6d631cf455
• 68d679b7bd7d371c5266d4803f03f204893f7af2
• a90161907aedae371cb307759b685cc254efe2d8
• dda5c72c9303f9476ce7041743c87079cada87f6
• 4d4fa685c0b507b510ad899f5afe94bd6c836115
• e95d2fefefb62150e566f000a4a17f58f6716af5
• 916bc93138f7a81f65c2e8b5069eeb0f35fceb43
• edd77531f8847f7b13dbaca9aefa315ba4aa5e57
• e70027f838f766b816bd1f7063514c1a9caf7a20
• 92dc76438063e68f7523d5ab036a57d7faf7bc03
• d1b22ff825052d836b56f8ce33760d42b2241980
• a76482c4614a7660ab2d324ca4c086f66906c701

The fix will be available with the upcoming 2.4.3 release.

[Adel-Magebinary]

Still happens in 2.4.2