-
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
flush cache before segment merge #4955
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. |
/run-all-tests |
Coverage for changed files
Coverage summary
full coverage report (for internal network access only) |
/run-all-tests |
Coverage for changed files
Coverage summary
full coverage report (for internal network access only) |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created: #4966. |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created: #4967. |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created: #4968. |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created: #4969. |
In response to a cherrypick label: new pull request created: #4970. |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created: #4971. |
* flush cache before segment merge * keep flush until success * check whether segment is valid if flush failed * Update dbms/src/Storages/DeltaMerge/tests/gtest_dm_segment.cpp Co-authored-by: JaySon <tshent@qq.com> * add more fix * check flush result in segment::write Co-authored-by: lidezhu <lidezhu@pingcap.com> Co-authored-by: lidezhu <47731263+lidezhu@users.noreply.github.com> Co-authored-by: JaySon <tshent@qq.com>
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
* This is an automated cherry-pick of #4955 Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io> * Update DeltaMergeStore.cpp * Fix conflict * fix build * try fix unit test * fix unit test fail
What problem does this PR solve?
Issue Number: close #4956
Problem Summary:
When do segment split, we try to copy the tail column files in the delta layer of the original segment to the new result
segments. So the new segments may contain data that doesn't belong to its segment range.
And this is ok for most cases, because the redundant data will be filtered out by the segment range when serve the read requests to the segment. So the redundant is invisible in almost all cases.
But when do segment merge later, if the previous redundant data is still not flushed to disk, it will be directly copied to the new merged segment again.
So the redundant data in each segment become visible again after segment merge which may cause potential data incorrectness.
What is changed and how it works?
Flush cache before every merge operation. So the potential unsaved data will be filtered out by the segment range when do merge.
Check List
Tests
Side effects
Documentation
Release note