[BugFix] fix mem leak when caching mv plan context (backport #72300)#72390
Conversation
Signed-off-by: kaijian.ding <kaijian.ding@gmail.com> (cherry picked from commit 33ccc4a) # Conflicts: # fe/fe-core/src/test/java/com/starrocks/planner/MaterializedViewTextBasedRewriteTest.java
|
Cherry-pick of 33ccc4a 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 |
|
@mergify[bot]: Backport conflict, please reslove the conflict and resubmit the pr |
|
@copilot fix the backport conflict in single commit, don't edit pull request description. |
Agent-Logs-Url: https://github.com/StarRocks/starrocks/sessions/3b691f9b-73a0-489a-b822-714734858a99 Co-authored-by: kevincai <771299+kevincai@users.noreply.github.com>
Head branch was pushed to by a user without write access
Fixed in 684a365. I resolved the backport conflict in Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
Why I'm doing:
There are lots of
LakeTabletobject on FOLLOWER after frequently drop&create same materialized view.And objects can't be releazed after fe transfers to LEADER.
What I'm doing:
Removed dropped materialized view object from pending cache and double check materialized view still exists before be added to context cache.
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
Checklist:
Bugfix cherry-pick branch check:
This is an automatic backport of pull request #72300 done by [Mergify](https://mergify.com).