[BugFix] Fix bRPC stub cache clean timer leak (backport #75973)#76361
[BugFix] Fix bRPC stub cache clean timer leak (backport #75973)#76361mergify[bot] wants to merge 4 commits into
Conversation
Signed-off-by: kaijian.ding <kaijian.ding@gmail.com> Co-authored-by: wanpengfei-git <wanpengfei91@163.com> (cherry picked from commit 2bbca67) # Conflicts: # be/src/util/brpc_stub_cache.cpp # be/src/util/brpc_stub_cache.h # be/test/util/brpc_stub_cache_test.cpp
|
Cherry-pick of 2bbca67 has failed: To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
Pull request was closed
|
@mergify[bot]: Backport conflict, please reslove the conflict and resubmit the pr |
@copilot fix backport conflicts |
@copilot please fix backport conflicts |
Head branch was pushed to by a user without write access
|
... Addressed in commit 6ed30fa. The backport conflicts are resolved and the branch now contains the conflict-free implementation and test updates.
... Fixed in commit 6ed30fa. I resolved the backport conflicts in |
Head branch was pushed to by a user without write access
Why I'm doing:
there is mem leak caused by bRPC stub cache clean timer leak due to timer is unscheduled but not removed from mem.
every
get_stub()will do_timer->unschedule()and_timer->schedule().unlike what we expect,
_timer->unschedule()will not remove internal objects, thus leak happensWhat I'm doing:
extend timer deadline if the stub is still in use instead of
unschedule()Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check:
This is an automatic backport of pull request #75973 done by [Mergify](https://mergify.com).