Rosa Gutierrez

Hey @cesarho, sorry about that! Could you share the `LATEST DETECTED DEADLOCK` section if you run `SHOW ENGINE INNODB STATUS` in your MySQL server?

Hey @cesarho, sorry for the delay in replying. Could you let me know your `queue.yml` configuration? I'm interested mostly in the `threads` value. I wonder if it'd be possible to...

Also, could you let me know the concurrency limits configuration for `CalcForShopJob`?

Hey @cesarho, sorry for the radio-silence and delay here! I see the threads value is pretty high indeed. Having concurrency controls in `CalcForShopJob` means using `perform_all_later` won't do anything, it'll...

Hey @wflanagan, [we already have support for this situation that you describe](https://github.com/basecamp/solid_queue?tab=readme-ov-file#threads-processes-and-signals): > If processes have no chance of cleaning up before exiting (e.g. if someone pulls a cable somewhere),...

> Are you saying it cleans up in this situation when there's not an opportunity for a graceful shutdown? Yes, exactly that, that's the exact situation I designed for, and...

> Ok. Maybe it was the version. This has been like this from the first version 😕 > I had "running jobs" for 18 days that were connected to workers...

@wflanagan, so, for Solid Queue, it's not possible to delete workers without deleting their assigned jobs because [that's done in a transaction](https://github.com/basecamp/solid_queue/blob/d71aa8ad6dd435fc458fc07be5ecc3b0cf4e89de/app/models/solid_queue/process.rb#L12), via an `after_destroy` callback. If workers are deleted...

> Any cloud infrastructure could/would have something like this happen. It's a pretty typical scenario. Yes, it can also happen in our case, and why we handle this via heartbeats...

Thank you! > The entire process in the worker that runs is run with bundle exec solidqueue:start. This entire process gets killed. So, wouldn't that kill the 5 threads and...