-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
tikv: fix panic after sending fail with ambiguous errors #17211
tikv: fix panic after sending fail with ambiguous errors #17211
Conversation
@hicqu PTAL, and maybe need help to recheck tikv's impl |
ref tikv/tikv#7324 and #15943 - - |
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
@jackysp need a approve |
/merge |
/run-all-tests |
Codecov Report
@@ Coverage Diff @@
## master #17211 +/- ##
===========================================
Coverage 79.8423% 79.8423%
===========================================
Files 520 520
Lines 139897 139897
===========================================
Hits 111697 111697
Misses 19236 19236
Partials 8964 8964 |
cherry pick to release-3.0 in PR #17378 |
cherry pick to release-3.1 in PR #17379 |
cherry pick to release-4.0 in PR #17380 |
What problem does this PR solve?
Issue Number: close #17201
Problem Summary:
batch client cleans up request map after sending fail, but tikv have the chance to receive requests when some ambiguous error happened.
and we should get panic when tikv make responses to those ambiguous requests now
What is changed and how it works?
Proposal: xxx
What's Changed:
log instead of panic
Related changes
Check List
Tests
Side effects
Release note
This change is