-
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.
64734: bulk: stop splitting on range flushes during RESTORE r=dt a=pbardea The SST batcher maintains logic to preemptively split a range when it sees the first size flush. However, we only want to do this when the SST batcher is enabled to split and scatter ranges after consuming a certain amount of data (which is indicated by setting the SplitAfter setting). SplitAfter is enabled by default when the SST batcher is used by the bulk adder (e.g. in IMPORT and backfills). In other cases (ie RESTORE), spans are already pre-split so this splitting and scattering is detrimental to RESTORE performance (range leaseholders get moved after they went through the split and scattering process). Release note: None 65029: bazel: handle `mockgen` in Bazel sandbox r=rail a=rickystewart There's an open-source library to do this for us, and it works well enough, so I just pull it in and use it everywhere we call into `mockgen`. Now there's only one un-bazelfied `go:generate` in-tree: `pkg/server/api_v2.go` :) Release note: None Co-authored-by: Paul Bardea <[email protected]> Co-authored-by: Ricky Stewart <[email protected]>
- Loading branch information
Showing
8 changed files
with
97 additions
and
15 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