-
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
*: Use strict validation for stale read ts & flashback ts (#57050) #58409
*: Use strict validation for stale read ts & flashback ts (#57050) #58409
Conversation
9ea565e
to
24d5d36
Compare
1eb5b3e
to
d8655c0
Compare
d8655c0
to
aa9ba4c
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cfzjywxk, ekexium 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 |
/retest |
61710ce
to
b02c042
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## release-6.5 #58409 +/- ##
================================================
Coverage ? 73.6224%
================================================
Files ? 1097
Lines ? 353046
Branches ? 0
================================================
Hits ? 259921
Misses ? 76388
Partials ? 16737 |
This is an automated cherry-pick of #57050
What problem does this PR solve?
Issue Number: close #56809
Problem Summary:
What changed and how does it work?
Use strict check for stale read ts & flashback ts to avoid any reading on future ts, which has risk to break the linearizability of async commit and 1PC transactions.
Pending and waiting for tikv/client-go#1484
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.