[DocDB] TableLocks: Handle abort of a deadlocked virtual transaction #24628
Labels
area/docdb
YugabyteDB core features
kind/new-feature
This is a request for a completely new feature
priority/medium
Medium priority issue
status/awaiting-triage
Issue awaiting triage
Jira Link: DB-13685
Description
Once #24596 lands, we could run into scenarios where the deadlock cycle contains virtual txns alone and no regular distributed txn (with object locks / advisory locks enabled).
We need to handle the abort path for a virtual transaction. We should have a mechanism to unblock the waiting requests at the object lock manager (as there is no regular txn, all the waiting requests would have been at the OLM itself), but not abort the virtual txn itself (since that corresponds to the host pg session).
Issue Type
kind/new-feature
Warning: Please confirm that this issue does not contain any sensitive information
The text was updated successfully, but these errors were encountered: