Skip to content
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

Handle database serialization deadlocks #712

Open
DeeTheDev opened this issue Sep 23, 2024 · 0 comments
Open

Handle database serialization deadlocks #712

DeeTheDev opened this issue Sep 23, 2024 · 0 comments
Labels
backend Involves changes to the backend API bug Something isn't working

Comments

@DeeTheDev
Copy link
Collaborator

DeeTheDev commented Sep 23, 2024

There are serialization lock failures that occur when there's multiple transactions inserting/updating the same row. This likely occurs when we insert and update a ledger, while we run async jobs that may run at the same instance.

Not entirely sure how to test this failure but we can definitely handle different serialization isolation levels with sequel.

@DeeTheDev DeeTheDev added bug Something isn't working backend Involves changes to the backend API labels Sep 23, 2024
@DeeTheDev DeeTheDev added this to the Purgatory milestone Sep 23, 2024
@DeeTheDev DeeTheDev changed the title Handle database serialization blocks Handle database serialization deadlocks Sep 23, 2024
@rgalanakis rgalanakis modified the milestones: Purgatory, 2024 Sprint 12 Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Involves changes to the backend API bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants