-
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
Some tables may not be physically dropped on TiFlash #8395
Labels
Comments
JaySon-Huang
added
type/bug
The issue is confirmed as a bug.
severity/moderate
component/storage
affects-7.5
labels
Nov 20, 2023
This was referenced Nov 26, 2023
12 tasks
This was referenced Nov 30, 2023
JaySon-Huang
added a commit
to ti-chi-bot/tiflash
that referenced
this issue
Nov 30, 2023
JaySon-Huang
added a commit
to ti-chi-bot/tiflash
that referenced
this issue
Nov 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
There is a chance that the
drop table
is executed on TiFlash before theIStorage
instance is actually created byapplying snapshot
.Then the information that the table has been dropped is missed on the TiFlash instance and its related data can not be physically dropped.
This can be workaround by restarting TiFlash, which will re-sync all table info from TiDB. And it will mark the table as tombstones at that time.
logging from testing pipeline : table_id_571.log
2. What did you expect to see? (Required)
3. What did you see instead (Required)
4. What is your TiFlash version? (Required)
https://github.com/pingcap/tiflash/tree/5ba01c04abc057f376eb71c8598cab65bc711460
The text was updated successfully, but these errors were encountered: