-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
39765: storage: introduce fine-grained latch acquisition r=irfansharif a=irfansharif Towards #32583. The current mechanism in place for declaring latches over MVCC keys only allows them to be declared at a fixed timestamp (on a per request basis). For split commands for e.g., we're interested in in declaring latches on different timestamps for the two sides of the split. Specifically we're interested in declaring a non-MVCC read latch over the LHS and a non-MVCC write latch over the RHS to be able to service reads during splits (requests without timestamps, i.e. the empty timestamp, are considered non-MVCC). The same ideas can be applied to range merges and lease transfers. This change allows callers to assign timestamps to latch acquisitions on a per latch basis so the optimizations above are made possible. Release note: None Co-authored-by: irfan sharif <[email protected]>
- Loading branch information
Showing
35 changed files
with
1,160 additions
and
398 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.