-
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
exeuctor: fix coprocessor goroutine leak for IndexMerge (#41610) #41655
exeuctor: fix coprocessor goroutine leak for IndexMerge (#41610) #41655
Conversation
Signed-off-by: guo-shaoge <shaoge1994@163.com>
Signed-off-by: guo-shaoge <shaoge1994@163.com>
Signed-off-by: guo-shaoge <shaoge1994@163.com>
Signed-off-by: guo-shaoge <shaoge1994@163.com>
Signed-off-by: guo-shaoge <shaoge1994@163.com>
Signed-off-by: guo-shaoge <shaoge1994@163.com>
Signed-off-by: guo-shaoge <shaoge1994@163.com>
[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: 32fd859
|
This is an automated cherry-pick of #41610
What problem does this PR solve?
Issue Number: close #41605
Problem Summary: As issue said, for partialIndexWorker and partialTableWorker of IndexMerge, we may failed to call
SelectResult.Close
when got panic(oom) inIndexMerge.fetchHandles()
. Therefore goroutines in coprocessor that tries to send copResp will stuck, because receiver already panic andcopIterator.finishCh
is never closed.What is changed and how it works?
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.