-
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
*: upgrade client-go to fix backoff panic #25865
*: upgrade client-go to fix backoff panic #25865
Conversation
Signed-off-by: youjiali1995 <[email protected]>
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
@cfzjywxk: Please use GitHub review feature instead of For the reason we drop support to the commands, see also this page. 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 ti-community-infra/tichi repository. |
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: e60e589
|
Signed-off-by: youjiali1995 [email protected]
What problem does this PR solve?
Problem Summary: close #25778
TiDB panics when resolving async-commit locks because it uses the same backoff concurrently.
What is changed and how it works?
What's Changed:
Fix it in client-go tikv/client-go#201 and upgrade it in TiDB.
Related changes
Check List
Tests
Release note