-
Notifications
You must be signed in to change notification settings - Fork 720
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
client/retry: only return the latest error in backoffer #8227
Conversation
[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. |
612870a
to
ce72132
Compare
// SetRetryableChecker sets the retryable checker. | ||
func (bo *Backoffer) SetRetryableChecker(checker func(err error) bool) { | ||
// SetRetryableChecker sets the retryable checker, `overwrite` flag is used to indicate whether to overwrite the existing checker. | ||
func (bo *Backoffer) SetRetryableChecker(checker func(err error) bool, overwrite bool) { |
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.
Isn't overwrite
over-designed? Because now there is only one call
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.
The SetRetryableChecker
function might be invoked by higher-level callers such as BR, Lightning, or TiDB. I added this flag to ensure the caller-set checker is not overwritten unexpectedly.
Signed-off-by: JmPotato <[email protected]>
Signed-off-by: JmPotato <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #8227 +/- ##
==========================================
+ Coverage 77.32% 77.38% +0.06%
==========================================
Files 470 471 +1
Lines 61340 61346 +6
==========================================
+ Hits 47431 47475 +44
+ Misses 10331 10303 -28
+ Partials 3578 3568 -10
Flags with carried forward coverage won't be shown. Click here to find out more. |
@okJiang: Thanks for your review. The bot only counts approvals from reviewers and higher roles in list, but you're still welcome to leave your comments. In response to this: 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. |
/merge |
@JmPotato: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger
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. |
This pull request has been accepted and is ready to merge. Commit hash: 5126a32
|
ref tikv#8142 Signed-off-by: ti-chi-bot <[email protected]>
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: JmPotato <[email protected]>
Signed-off-by: JmPotato <[email protected]>
Signed-off-by: JmPotato <[email protected]>
Signed-off-by: JmPotato <[email protected]>
ref #8142, close #8499 Due to the return of historical errors causing the client's retry logic to fail, and since we currently do not need to obtain all errors during retries, this PR removes `multierr` from backoffer and add tests to ensure the correctness of the retry logic. Signed-off-by: JmPotato <[email protected]> Co-authored-by: JmPotato <[email protected]>
What problem does this PR solve?
Issue Number: ref #8142.
What is changed and how does it work?
Check List
Tests
Release note