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

[DocDb] Optimize deadlock detection to detect conflicts local to tserver when present #13586

Open
robertsami opened this issue Aug 11, 2022 · 1 comment
Open

[DocDb] Optimize deadlock detection to detect conflicts local to tserver when present #13586

robertsami opened this issue Aug 11, 2022 · 1 comment
Assignees
@basavaraj29
Labels
area/docdb YugabyteDB core features kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue
Projects
Wait-Queue Based Locking

Comments

@robertsami
Copy link
Contributor

robertsami commented Aug 11, 2022 •
edited by jira bot

Jira Link: DB-3162
We can detect some deadlocks without relying on distributed deadlock detection by just looking at local wait-for relationships. We can do this for a new waiting transaction /before/ sending information about this waiting transaction to the txn coordinator
@robertsami robertsami added the area/docdb YugabyteDB core features label Aug 11, 2022
@robertsami robertsami self-assigned this Aug 11, 2022
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug priority/medium Medium priority issue labels Aug 11, 2022
@robertsami robertsami mentioned this issue Aug 17, 2022
Closed
@yugabyte-ci yugabyte-ci added kind/enhancement This is an enhancement of an existing feature and removed kind/bug This issue is a bug labels Sep 3, 2022
@robertsami robertsami moved this from Needs Triage to Backlog in Wait-Queue Based Locking Jan 17, 2023
@robertsami robertsami changed the title [dst] Detect deadlocks locally among local WaitQueue instances [dst] Optimize deadlock detection to detect conflicts locally when present Jun 26, 2023
@robertsami robertsami changed the title [dst] Optimize deadlock detection to detect conflicts locally when present [dst] Optimize deadlock detection to detect conflicts local to tserver when present Jun 26, 2023
@rthallamko3
Copy link
Contributor

This is important, if the performance impact of deadlock detection is high and if there is a need to reduce it.

@rthallamko3 rthallamko3 changed the title [dst] Optimize deadlock detection to detect conflicts local to tserver when present [DocDb] Optimize deadlock detection to detect conflicts local to tserver when present May 4, 2024
@rthallamko3 rthallamko3 assigned basavaraj29 and unassigned robertsami May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@basavaraj29 basavaraj29

Labels
area/docdb YugabyteDB core features kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue
Projects
Wait-Queue Based Locking
Status: Pending
Wait-Queue Based Locking
Backlog
Milestone
No milestone
Development

No branches or pull requests
4 participants
@robertsami @rthallamko3 @yugabyte-ci @basavaraj29