-
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: start with all the system ranges at bootstrap
Before this patch, a store would be bootstrapped with a single range, and then we'd rely on the split queue to create splits at a statically defined list of keys and between system tables. This patch changes the bootstrapping so that the store starts up with all these ranges and we don't rely on the split queue any more. This simplifies thigs: less moving pieces for new clusters. Besides that, there was a problem before since all the ranges deriving from the original mother one were starting with expiration-based leases. Once those expired, most of them would transition to epoch-based leases. That transition is disruptive - clears the timestamp cache and such - and so transactions running at those times (4.5s after cluster startup) would incur restarts. This was a problem for tests. Also, the fact that ranges were starting up with expiration-based leases was also a problem for rangefeed tests since rangefeeds don't work on those ranges (as I understand it). As a result of this patch, a bunch of different tests now run with more realistic stores: there are a million ways to create stores in tests and most of them before were just getting a single range; now most get many. Fixes #32495 Fixes #31182 Fixes #31065 Release note: None
- Loading branch information
1 parent
046cca2
commit 352bdf4
Showing
58 changed files
with
1,671 additions
and
941 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
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
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.