resolved-ts: use min_lock_ts-1 as the candidate of resolved-ts#17730
resolved-ts: use min_lock_ts-1 as the candidate of resolved-ts#17730ti-chi-bot[bot] merged 6 commits intotikv:masterfrom
Conversation
bd8126f to
3e2c1e9
Compare
Signed-off-by: ekexium <eke@fastmail.com>
3e2c1e9 to
d200ea1
Compare
…ual-min-commit-ts
|
/retest |
…nt resolved-ts decreasing across TiKV upgrades. Signed-off-by: ekexium <eke@fastmail.com>
953ecb2 to
5e56746
Compare
…ual-min-commit-ts
5e56746 to
8b7a2db
Compare
Co-authored-by: you06 <you1474600@gmail.com> Signed-off-by: ekexium <eke@fastmail.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cfzjywxk, you06 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@ekexium: Your PR was out of date, I have automatically updated it for you. 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. DetailsInstructions 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. |
|
/retest |
|
In response to a cherrypick label: new pull request created to branch |
…17730) close tikv#17728 Use min_lock_ts-1 as the candidate of resolved-ts, to ensure resolved_ts < lock.min_commit_ts( <= commit_ts). Signed-off-by: ekexium <eke@fastmail.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com> Co-authored-by: you06 <you1474600@gmail.com>
… (#17768) close #17728 Use min_lock_ts-1 as the candidate of resolved-ts, to ensure resolved_ts < lock.min_commit_ts( <= commit_ts). Signed-off-by: ekexium <eke@fastmail.com> Co-authored-by: ekexium <eke@fastmail.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com> Co-authored-by: you06 <you1474600@gmail.com>
What is changed and how it works?
Issue Number: Close #17728
What's Changed:
The problem
By the definition of resolved-ts, we require:
commit_ts > resolved_ts, if the commit happens after the calculation of the resolved-ts.Our implementation uses min_commit_ts to calculate resolved-ts, so that what we have is:
commit_ts >= min_commit_ts >= resolved_tsresolved_tsmay be equal tocommit_ts, which breaks the definition of resolved-ts.The fix
This PR ensures
min_commit_ts > resolved_tsto fix the problemRelated changes
pingcap/docs/pingcap/docs-cn:Check List
Tests
Side effects
Release note