-
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.
storage: use lease start time to determine follower read safety
This change recognizes that lease transfer start times have provide write invariants equivalent to those provided by the closed timestamp and MLAI and thus the maximum closed timestamp for a replica can be viewed as the maximum timestamp of that of the current replica lease start time and the timestamp provided by the closed timestamp provider. Utilizing this fact makes follower reads as well as rangefeeds more robust to lease transfers. Before this change lease transfers to different nodes might cause closed timestamp information for a range to become unavailable leading to an inability for a range to serve a read at a timestamp which was previously determined to be safe. Fixes #35129. Release note: None
- Loading branch information
Showing
7 changed files
with
297 additions
and
184 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
Oops, something went wrong.