Cleanup Job crashes MySQL

[tim]

I observe quite an interesting behavior. If "Cleanup" job is executed via cron once a week (default schedule) it crashes MySQL (MySQL has gone away). If I run it manually via "bin/command run-job Cleanup" it does take a while but finishes fine. If I run it manually day before scheduled job the cron job also finishes fine on the next run.

Any ideas what could cause it? Any workarounds? Maybe changing the schedule to run the job on a daily basis?

[yuri]

It could because of different environment used when running from cron – different parameters applied. But have not no idea what is exact reason.

[tim]

What would be the proper way to change Cleanup job schedule to run every hight?

[yuri]

Administration > Scheduled Jobs > Cleanup. Then, you can edit Scheduling in crontab notation.

[goingUp]

Any ideas what could cause it?

Maybe Mysql uses too much memory and is killed by OOM killer. It can cause "MySQL has gone away" error. Fix is to adjust memory limits in Mysql.

[yuri]

Or timeout. The Cleanup job should not consume a lot of memory as far as I know.

[tim]

Yes. It is heavy on CPU, not memory:



Curiously enough is that slowest queries are scheduled_job_log_record select and delete


Those are just log records, right?

[yuri]

Hope it will be taking less resources in v9.0. These are scheduled job log records.