-
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: record latest schema version after syncer restarted (#49929) #50247
domain: record latest schema version after syncer restarted (#49929) #50247
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## release-7.1 #50247 +/- ##
================================================
Coverage ? 74.5408%
================================================
Files ? 1211
Lines ? 389372
Branches ? 0
================================================
Hits ? 290241
Misses ? 81595
Partials ? 17536 |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Benjamin2037, tangenta 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:
|
This is an automated cherry-pick of #49929
What problem does this PR solve?
Issue Number: close #49773
Problem Summary:
The start ts of two DML txns is close, but the schema version differs(55 v.s. 58). The txn with schemaVersion = 55 first obtains the info schema from the cache before the restoration of network partition (that is, the domain has not been successfully reloaded). When it commit later, because MDL is enabled, the schema validator check will be skipped, resulting in the commit of data under an old schema (index state is
write-reorg
, backfilling state isBackfillStateRunning
, the write is redirected to temporary index), which further leads to inconsistent data indexes.Here is the timeline:
What changed and how does it work?
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.