-
Notifications
You must be signed in to change notification settings - Fork 121
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
Pessimistic lock errors with the heartbeat #350
Comments
Oh, that's a strange one! Let me look into it. |
Do you get any errors before this, when Solid Queue starts, when registering any of the processes (dispatchers, workers, etc.)? You should get some lines like this:
I have a suspicion of what this might be about... |
Thank you! That's very helpful 🙏 |
Huh, ok, that's unexpected and changed what I thought this was about 😅 😅 Did you get any errors of other kind before the lock errors started? |
Aha! Now everything makes sense 😆 Ok, I'll get this fixed. |
For example, in case of a previous heartbeat failed because of a DB issue (with SQLite depending on configuration, a `BusyException` is not rare) and we still have the unpersisted value in `last_heartbeat_at`, which means that `with_lock` will result in: ``` RuntimeError: Locking a record with unpersisted changes is not supported ``` Fixes #350
For example, in case of a previous heartbeat failed because of a DB issue (with SQLite depending on configuration, a `BusyException` is not rare) and we still have the unpersisted value in `last_heartbeat_at`, which means that `with_lock` will result in: ``` RuntimeError: Locking a record with unpersisted changes is not supported ``` Fixes #350
I get a lot of pessimistic lock errors. Something around every minute because of the heartbeat.
The error:
Backtrace:
Is there something i can do on my side?
Running:
What else do you need from me?
The text was updated successfully, but these errors were encountered: