-
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
Fix sync schema after schema version key be removed #7072
Conversation
Signed-off-by: yongman <[email protected]>
[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. |
/cc @iosmanthus |
if (version == -1 && cur_version == version) | ||
{ | ||
// Tables and databases are already tombstoned and waiting for GC. | ||
return false; | ||
} |
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.
I think it's too implicit, the reader does not know the table's dropped in builder.syncAllSchemas
. How about constructing a builder here and calling applyDropSchema for each table/database explicitly? /cc @JaySon-Huang
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 about constructing a builder here and calling applyDropSchema for each table/database explicitly?
Is there a chance that SchemaGetter::getVersion
get -1
, but the tables and databases metadata on TiKV does not get fully cleaned yet?
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.
I think it's too implicit
I agree, now it is kind of complicated, we can add a shortcut logic when version < 0 to skip some codes and make the flow more clear.
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.
Is there a chance that
SchemaGetter::getVersion
get-1
, but the tables and databases metadata on TiKV does not get fully cleaned yet?
I think partial deletion of an entire keyspace is illegal.
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 the Regions of a "deleted" keyspace get removed from TiKV? Are they removed one by one?
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.
@JaySon-Huang No, the keyspace range will be delete in two UnsafeDestroyRange
requests, one for transaction kv space, the other for raw kv space.
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.
I agree that it's better make the logic more direct, the logic now is to treat the version=-1
as same as version>=0
to sync schema, but return ASAP in tryLoadSchemaDiffs
if version=-1
.
Emm, is it necessary to implement a branch to syncAllSchemas
and maintain the metrics ? 🤦 /cc @JaySon-Huang @iosmanthus
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.
Considering of possibility inconsistency of getVersion
and listDBs
after UnsafeDestroyRange
, we do not need to listDB
or listTables
if the schema version key not exists. It‘s neccessary to run shortcut logic in this case. We can add a new method SchemaBuilder::dropAllSchema()
to resolve this. /cc @JaySon-Huang @iosmanthus
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
Signed-off-by: JaySon-Huang <[email protected]>
Co-authored-by: JaySon <[email protected]>
Signed-off-by: yongman <[email protected]>
@JaySon-Huang @iosmanthus PTAL |
Signed-off-by: yongman <[email protected]>
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.
The rest LGTM
Signed-off-by: yongman <[email protected]>
/run-all-tests |
for (auto it = storage_map.begin(); it != storage_map.end(); it++) | ||
{ | ||
auto table_info = it->second->getTableInfo(); | ||
if (table_info.keyspace_id != keyspace_id) | ||
{ | ||
continue; | ||
} | ||
applyDropPhysicalTable(it->second->getDatabaseName(), table_info.id); | ||
LOG_DEBUG(log, "Table {}.{} dropped during drop all schemas", it->second->getDatabaseName(), name_mapper.debugTableName(table_info)); | ||
} |
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.
better to use Range-based for loop
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.
@Lloyd-Pottiger This code block is copied from syncAllSchemas, we should keep the code style same?
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.
no, improve it, I think.
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.
PTAL~
Signed-off-by: yongman <[email protected]>
/merge |
@Lloyd-Pottiger: 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: 80a2e5b
|
@yongman: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests
If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. 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. |
What problem does this PR solve?
Issue Number: close #7071
Problem Summary:
What is changed and how it works?
If schema version key for keyspace not exists, load all schema and tombstone tables and databases in this keyspace.
Check List
Tests
Side effects
Documentation
Release note