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.

Sign up for GitHub

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

Jump to bottom

Transaction Deadlock when fetching large amount of tuples in parallel #46

Open
sbckr opened this issue Jan 30, 2023 · 0 comments
Open

Transaction Deadlock when fetching large amount of tuples in parallel #46

sbckr opened this issue Jan 30, 2023 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@sbckr
Copy link
Member

sbckr commented Jan 30, 2023

A transaction deadlock may occur when large amounts of tuples (occurred when requesting 580.000 InputMasks) are requested from Castor, especially with concurrent requests in place.

Quick-Fix

The likelihood of a deadlock occurring could be reduced by increasing the default fragment size from 1000 tuples to a more reasonable number such as 100,000 tuples. This significantly reduces the number of database queries when creating and sharing tuple reservation.

Logs

Logs currently not available.
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jan 30, 2023
@strieflin strieflin added kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@strieflin @sbckr