-
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
localbackend: fix resource leak when err on new local backend #53664
Conversation
Hi @D3Hunter. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with I understand the commands that are listed here. 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 kubernetes-sigs/prow repository. |
@@ -112,7 +112,7 @@ func PaginateScanRegion( | |||
var batch []*RegionInfo | |||
batch, err = client.ScanRegions(ctx, scanStartKey, endKey, limit) | |||
if err != nil { | |||
err = errors.Annotatef(berrors.ErrPDBatchScanRegion, "scan regions from start-key:%s, err: %s", | |||
err = errors.Annotatef(berrors.ErrPDBatchScanRegion.Wrap(err), "scan regions from start-key:%s, err: %s", |
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.
make sure we can see context cancel as a error, not a string
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #53664 +/- ##
================================================
+ Coverage 74.4613% 75.0389% +0.5775%
================================================
Files 1506 1528 +22
Lines 357521 439893 +82372
================================================
+ Hits 266215 330091 +63876
- Misses 71899 89150 +17251
- Partials 19407 20652 +1245
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: GMHDBJD, lance6716, Leavrth The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/run-cherry-pick |
/run-cherrypick |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created to branch |
What problem does this PR solve?
Issue Number: close #53659
Problem Summary:
What changed and how does it work?
Check List
Tests
i think it's too much to add so many failpoints to just test resource closed on err, so i write the test here
apply this diff to the code
then in real-tikv-test which have routine leak check, add this:
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.