-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
backup: support split big region into small backup files (#9283) #9448
backup: support split big region into small backup files (#9283) #9448
Conversation
Signed-off-by: ti-srebot <[email protected]>
Signed-off-by: Chunzhu Li <[email protected]>
Signed-off-by: Chunzhu Li <[email protected]>
Signed-off-by: Chunzhu Li <[email protected]>
/lgtm |
@kennytm: In response to this:
Instructions 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 ti-community-infra/ti-community-prow repository. |
/lgtm |
/label do-not-merge/cherry-pick-not-approved |
This cherry pick PR is for a release branch and has not yet been approved by release team. To merge this cherry pick, it must first be approved (/lgtm + /merge) by the collaborators. AFTER it has been approved by collaborators, please psend an email to the QA team requesting approval and the QA team will help you merge the PR. |
@overvenus PTAL |
/label cherry-pick-approved |
/lgtm |
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by writing |
/merge |
@NingLin-P: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger If you have any questions about the PR merge process, please refer to pr process. Instructions 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 ti-community-infra/tichi repository. |
@NingLin-P: In response to this:
Instructions 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 ti-community-infra/tichi repository. |
/lgtm |
/run-all-tests |
/merge |
@overvenus: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger If you have any questions about the PR merge process, please refer to pr process. Instructions 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 ti-community-infra/tichi repository. |
This pull request has been accepted and is ready to merge. Commit hash: 828c71b
|
@ti-srebot: Your PR has out-of-dated, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests Instructions 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 ti-community-infra/tichi repository. |
cherry-pick #9283 to release-4.0
What problem does this PR solve?
Issue Number: close #9144
Problem Summary: BR will read all data of a region and fill it in a SST writer. But it is in-memory. If there is a huge region, TiKV may crash for OOM because of keeping all data of this region in memory.
What is changed and how it works?
What's Changed: Record the written txn entries' size. When it reaches
region_max_size
, we will save the data cached in RocksDB to a SST file and then switch to the next file.Related changes
Check List
Tests
sst-max-size
to 15MiB.Release note