You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2020/11/20 12:15:00 UTC
[jira] [Closed] (FLINK-12707) Close minicluster will cause memory
leak when there are StreamTask closed abnormal
[ https://issues.apache.org/jira/browse/FLINK-12707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Metzger closed FLINK-12707.
----------------------------------
Resolution: Duplicate
> Close minicluster will cause memory leak when there are StreamTask closed abnormal
> -----------------------------------------------------------------------------------
>
> Key: FLINK-12707
> URL: https://issues.apache.org/jira/browse/FLINK-12707
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.8.0
> Reporter: liuzhaokun
> Assignee: liuzhaokun
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> There are several threads in my application,and every thread will launch a flink job with LocalStreamEnvironment/MiniCluster.But when I interrupt these threads again and again, I found there are many residue threads,and that caused a memory leak.
> When I debug it,this message appears "Recipient[Actor[akka://flink/user/taskmanager_0#-584606215]] had already been terminated. Sender[null] sent the message of type "org.apache.flink.runtime.rpc.messages.LocalRpcInvocation". So I think
> when flink close minicluster,TaskExecutor will be closed in the first place,and this operation will cause akka message which will close StreamTask abnormal.So the work thread will be more and more.
> I call Thread sleep in my application to avoid this problem,any good suggestions?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)