[close #421] [br-release-1.0] br: Split for smaller batch of keys (#422)#423
Merged
pingyu merged 5 commits intotikv:br-release-1.0from Apr 16, 2025
Merged
[close #421] [br-release-1.0] br: Split for smaller batch of keys (#422)#423pingyu merged 5 commits intotikv:br-release-1.0from
pingyu merged 5 commits intotikv:br-release-1.0from
Conversation
Signed-off-by: Ping Yu <yuping@pingcap.com>
Signed-off-by: Ping Yu <yuping@pingcap.com>
|
@pingyu: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
zeminzhou
approved these changes
Apr 16, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry pick of #422
What problem does this PR solve?
Issue Number: close #421
Problem Description: br: split regions failed
What is changed and how does it work?
1024.split-region-max-keys = 4for integration tests.Code changes
Check List for Tests
This PR has been tested by at least one of the following methods:
Manually confirm the coverage of split region with max keys =
4by logs of integration tests.Side effects
Related changes
To reviewers
Please follow these principles to check this pull requests:
(The above text mainly refers to TiDB Development Guide. It's also highly recommended to read about Writing code review comments)