-
Notifications
You must be signed in to change notification settings - Fork 166
Deadlock found when trying to get lock; try restarting transaction #531
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
Hey @cesarho, sorry about that! Could you share the |
@rosa Really appreciated your help and creating solid queue. We are migrating the workload from Lambda to SolidQueue. To give you more context, we have set 3 scheduler jobs at 30 min interval.
Here is the log I extract this morning.
case 2
|
I think I have faced similar issues and resolved it by using |
Thanks @iJackUA I also encountered deadlock when using |
Hey @cesarho, sorry for the delay in replying. Could you let me know your DELETE FROM `solid_queue_ready_executions` WHERE `solid_queue_ready_executions`.`id` IN (695327, 695316, 695323, 695330, 695326, 695324, 695328, 695329, 695331, 695332, 695334, 695333) |
Also, could you let me know the concurrency limits configuration for |
@rosa No worry. Thanks for getting back. Is there any hints how should the worker thread and job currency setup on using solid queue?
The concurrency limit setting for
|
Hi,
I scheduled a few recurring job to run every hours. This job will trigger around 800 active jobs. here is the pseudo code:
I encountered the deadlock on the database. The MysQL is purely used for solid queue. MySQL version is 8.4. Is there precaution on using solid queue to prevent deadline?
Type | SolidQueue::Job::EnqueueError
ActiveRecord::Deadlocked: Mysql2::Error: Deadlock found when trying to get lock; try restarting transaction
The text was updated successfully, but these errors were encountered: