-
Notifications
You must be signed in to change notification settings - Fork 4.1k
kv: return error on locking request in LeafTxn #97817
Copy link
Copy link
Closed
Labels
A-kv-clientRelating to the KV client and the KV interface.Relating to the KV client and the KV interface.A-kv-transactionsRelating to MVCC and the transactional model.Relating to MVCC and the transactional model.C-cleanupTech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior.Tech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior.T-kvKV TeamKV Team
Description
In #94290, we saw that locking requests could be issued through a LeafTxn and the lock spans would be silently dropped, leading to delayed unlocking once the locker transaction was committed. We don't support locking requests passed through a LeafTxn, so we should assert against this and return an error to clients that issue such requests.
Jira issue: CRDB-25806
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-kv-clientRelating to the KV client and the KV interface.Relating to the KV client and the KV interface.A-kv-transactionsRelating to MVCC and the transactional model.Relating to MVCC and the transactional model.C-cleanupTech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior.Tech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior.T-kvKV TeamKV Team