[
https://issues.apache.org/jira/browse/FLINK-9930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16804864#comment-16804864
]
Till Rohrmann commented on FLINK-9930:
--------------------------------------
The best solution is to not use static variables in your user code. Otherwise
it will only be cleaned up after the class is being unloaded.
> Flink slot memory leak after restarting job with static variables
> -----------------------------------------------------------------
>
> Key: FLINK-9930
> URL: https://issues.apache.org/jira/browse/FLINK-9930
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.4.2
> Reporter: Martin Shang
> Priority: Critical
>
> I find flink taskmanager exit caused by OOM ,and I dumped the head file.
>
> The result is that the static variables are not released when canceled the
> job, and a new object is generated after I restarted the job.
> The static variable is multiple for the slot memory isolation.
> How could I make the variables collected by the Flink?
> [multiple static variable|https://i.stack.imgur.com/KJcIN.jpg]
> [path to gc|https://i.stack.imgur.com/bvrDF.jpg]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
