You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2019/06/07 12:46:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16858593#comment-16858593 ] 

Till Rohrmann commented on FLINK-12707:
---------------------------------------

Could this be caused by FLINK-11630? It sounds as if the {{Task}} threads are not being terminated. If this is the case, then please close this issue as a duplicate of FLINK-11630.

> 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: Improvement
>          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
(v7.6.3#76005)