ultimate_cron_lock high db size

Created on 24 January 2018, about 7 years ago
Updated 8 January 2025, 3 months ago

Hi there!

I am using UC to split my crons task, mostly for queues. We are receiving webhooks from external services and everything is queued. Each queues are processed every minutes.

I have a lot of queues and need to run multiple thread. I keep getting the error "Could not get lock ..." ( https://www.drupal.org/project/ultimate_cron/issues/2500811 💬 Could not get lock for job ... Closed: outdated ). After seeing the linked issue, I thought it was just a message showing up in the logs and even if not clean, that was still fine.

But yesterday, we realized that our table ultimate_cron_lock was over 2Gb ... We reduced launcher threads to 1, now we don't have the message and the table cleaned herself. But now, I have to manually increase the number of threads from time to time to make sure we are emptying queues fast enough. But every time I do this, the table start to get bigger and we get the error in the logs.

I had a look at the code, but I am having some hard time understanding the lock process, and what exactly is the purpose of that lock (I am sure it is an absolutely essential piece of UC, it is just me not getting it :) ). Why does a queue can get locked multiple times?

I will try to look at this better, I really need to find a way to make it work so I can spend some time on this.

Thanks for the work on this module, it is really saving my life every day !

Ed

🐛 Bug report
Status

Closed: outdated

Version

2.5

Component

Code

Created by

🇨🇦Canada heyddi

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇩🇰Denmark arnested

    I'm closing this since Drupal 7 is now unsupported and there will be no more development on the Drupal 7 branch of Ultimate Cron either.

    Thank you for taking the time and effort in reporting this issue, even though it never got resolved.

Production build 0.71.5 2024