-
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
ddl: Skip updating the tombstone_ts if the table is already tombstone (release-7.1) #9231
Merged
ti-chi-bot
merged 8 commits into
pingcap:release-7.1
from
JaySon-Huang:tombstone_repeat_71
Sep 3, 2024
Merged
ddl: Skip updating the tombstone_ts if the table is already tombstone (release-7.1) #9231
ti-chi-bot
merged 8 commits into
pingcap:release-7.1
from
JaySon-Huang:tombstone_repeat_71
Sep 3, 2024
Conversation
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
ti-chi-bot
bot
added
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
do-not-merge/cherry-pick-not-approved
size/S
Denotes a PR that changes 10-29 lines, ignoring generated files.
labels
Jul 12, 2024
ti-chi-bot
bot
added
the
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
label
Jul 12, 2024
Signed-off-by: JaySon-Huang <tshent@qq.com>
JaySon-Huang
force-pushed
the
tombstone_repeat_71
branch
from
July 15, 2024 06:15
63e72c4
to
a2e4d39
Compare
ti-chi-bot
bot
added
size/L
Denotes a PR that changes 100-499 lines, ignoring generated files.
and removed
size/S
Denotes a PR that changes 10-29 lines, ignoring generated files.
labels
Jul 15, 2024
Signed-off-by: JaySon-Huang <tshent@qq.com>
/run-all-tests |
ti-chi-bot
bot
removed
the
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
label
Jul 15, 2024
Lloyd-Pottiger
approved these changes
Sep 3, 2024
ti-chi-bot
bot
added
needs-1-more-lgtm
Indicates a PR needs 1 more LGTM.
approved
labels
Sep 3, 2024
/run-all-tests |
ti-chi-bot
bot
added
cherry-pick-approved
Cherry pick PR approved by release team.
and removed
do-not-merge/cherry-pick-not-approved
labels
Sep 3, 2024
JinheLin
approved these changes
Sep 3, 2024
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JinheLin, Lloyd-Pottiger The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ti-chi-bot
bot
added
lgtm
and removed
needs-1-more-lgtm
Indicates a PR needs 1 more LGTM.
labels
Sep 3, 2024
[LGTM Timeline notifier]Timeline:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approved
cherry-pick-approved
Cherry pick PR approved by release team.
lgtm
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
size/L
Denotes a PR that changes 100-499 lines, ignoring generated files.
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.
What problem does this PR solve?
Issue Number: close #9227
Problem Summary: #9227 (comment)
In
SchemaBuilder::syncAllSchema
, each table that does not exists in tikv but still in the tiflash instance. TiFlash will executeapplyDropPhysicalTable
for each table, wich will update the "tombstone_ts" of the table in its ".sql" file.Even if the table is already "tombstone", the function will update the "tombstone_ts" by a newer tso from PD. This make the IStorage instance still exist even after the gc_safepoint is exceed than the drop timepoint + gc_lifetime.
tiflash/dbms/src/TiDB/Schema/SchemaBuilder.cpp
Lines 1437 to 1451 in 28a2314
tiflash/dbms/src/TiDB/Schema/SchemaBuilder.cpp
Lines 1240 to 1268 in 28a2314
What is changed and how it works?
Skip updating the tombstone_ts if the table is already tombstone. So even if the "syncAllSchema" is called repeatedly, the dropped IStorage instance can be physically removed from TiFlash instances correctly. And the time spend on "syncAllSchema" won't become longer and longer.
Check List
Tests
Run the following test scripts. It will make tiflash run into sync all schema frequently.
In the v6.5.10 version, after that script ran,
Side effects
Documentation
Release note