-
Notifications
You must be signed in to change notification settings - Fork 409
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
add more checks for background segment split #4406
add more checks for background segment split #4406
Conversation
[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 submitting an approval review. |
|| delta_bytes - delta_last_try_split_bytes >= delta_cache_limit_bytes); | ||
// Do background split in the following two cases: | ||
// 1. The segment is large enough, and there are some data in the delta layer. (A hot segment which is large enough) | ||
// 2. The segment is too large. (A segment which is too large, although it is cold) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how do we trigger checkSegmentUpdate on a segment that is cold?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here is some intuition for the check condition in the comments. The actual problem is here: https://docs.google.com/document/d/1tkJXERVmcKv6nwfhTXqk0qTdVm2CPh8OXZiZ8ap6sOA/edit?usp=sharing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Cold" means no continuous small write in this segment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/merge |
@lidezhu: 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. |
Coverage for changed files
Coverage summary
full coverage report (for internal network access only) |
/run-integration-tests |
/merge |
@lidezhu: 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. |
@lidezhu: 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. |
Coverage for changed files
Coverage summary
full coverage report (for internal network access only) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/merge |
@flowbehappy: 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: aa00479
|
Coverage for changed files
Coverage summary
full coverage report (for internal network access only) |
In response to a cherrypick label: new pull request created: #4416. |
In response to a cherrypick label: new pull request created: #4417. |
What problem does this PR solve?
Issue Number: close #4408
Problem Summary: After syncing data from tikv using snapshot, there are some too large segments.
What is changed and how it works?
Add more check for background split.
Check List
Tests
Load tpch100 into tiflash(set tiflash replica after data loaded into tikv), and check the segments stat using query:
select
rows
from information_schema.tiflash_segments wheretable
="t_144" order byrows
;Before fix:
After fix:
Side effects
Documentation
Release note