concurrency_manager: check update_max_ts against a limit (#17917)#18049
Conversation
Signed-off-by: ekexium <eke@fastmail.com>
b6c199a to
2d40b5f
Compare
|
/retest |
…f invalid max-ts update (tikv#18057) close tikv#18055 concurrency_manager: double check via PD TSO before reporting error of invalid max-ts update Signed-off-by: ekexium <eke@fastmail.com>
ref tikv#18055 When validating max-ts updates, do not report error or panic unless confirmed by PD TSO. This reduces both false positive and false negative cases. Signed-off-by: ekexium <eke@fastmail.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
|
/retest |
1 similar comment
|
/retest |
Signed-off-by: ekexium <eke@fastmail.com>
[LGTM Timeline notifier]Timeline:
|
|
@ti-chi-bot: 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. |
|
/hold |
|
/unhold |
f27ddc7 to
7a7c3a8
Compare
|
/retest |
Signed-off-by: ekexium <eke@fastmail.com>
7a7c3a8 to
b2c29c5
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MyonKeminta, 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 |
|
/retest |
This is an automated cherry-pick of #17917
What is changed and how it works?
Issue Number: close #17916
What's Changed:
Metric:

Benchmark of
update_max_ts:master
This PR
Read operations typically need hundreds of microseconds, so I suppose this regression has little impact.
Related changes
pingcap/docs/pingcap/docs-cn:Check List
Tests
Side effects
Release note