-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
domain,infoschema: avoid v1/v2 switch when loading snapshot infoschema #55129
Conversation
Hi @tiancaiamao. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with I understand the commands that are listed here. 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 kubernetes-sigs/prow repository. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #55129 +/- ##
================================================
+ Coverage 72.9177% 74.3777% +1.4599%
================================================
Files 1568 1568
Lines 439181 439192 +11
================================================
+ Hits 320241 326661 +6420
+ Misses 99308 92133 -7175
- Partials 19632 20398 +766
Flags with carried forward coverage won't be shown. Click here to find out more.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lance6716, wjhuang2016 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 |
[LGTM Timeline notifier]Timeline:
|
/retest |
@tiancaiamao: Cannot trigger testing until a trusted user reviews the PR and leaves an 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 kubernetes-sigs/prow repository. |
/ok-to-test |
/retest |
/check-issue-triage-complete |
/retest |
/retest |
What problem does this PR solve?
Issue Number: close #55114
Problem Summary:
What changed and how does it work?
Compatibility between infoschema snapshot and v1&v2 switch is difficult.
snapshot needs the history, while v1&v2 swtich reset the infoschema history,
this conflict is the root cause of bugs like #55114 #54926
So what I do in this commit is to avoid such case happen together:
If it's a loading of snapshot infoschema, then avoid v1&v2 switch.
Now whether the infoschema builder should build v2 is not decided soly by
variable.SchemaCacheSize > 0
, it's also affect by whether this loading isSnapshot. Provide ashouldUseV2()
function for that.Check List
Tests
I try to add a unit test like this:
The test works well and prove the correctness of this change.
But it's not feasible to be added to unit test, because how long it runs is undetermined.
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.