[
https://issues.apache.org/jira/browse/FLINK-19005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181205#comment-17181205
]
Matthias commented on FLINK-19005:
----------------------------------
Hi Robert,
this looks like a Metaspace leak. The memory used for the Metaspace pool is
quite high comparing it to other use cases (e.g. in this [mailing list
thread|http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/MaxMetaspace-default-may-be-to-low-td33049.html#a33072]).
One proposal is to create a heap dump to check whether there are classes that
are not cleaned up. This could be either ab indication of Metaspace memory leak
in the user code or Flink. Would it be possible to analyse the heap dump
yourself or provide it for an assisted analysis? In the latter case, I would
propose moving the discussion into [User Mailing
List|https://flink.apache.org/community.html#mailing-lists].
Best,
Matthias
> used metaspace grow on every execution
> --------------------------------------
>
> Key: FLINK-19005
> URL: https://issues.apache.org/jira/browse/FLINK-19005
> Project: Flink
> Issue Type: Bug
> Components: API / DataSet, Client / Job Submission
> Affects Versions: 1.11.1
> Reporter: Guillermo Sánchez
> Priority: Major
>
> Hi !
> Im running a 1.11.1 flink cluster, where I execute batch jobs made with
> DataSet API.
> I submit these jobs every day to calculate daily data.
> In every execution, cluster's used metaspace increase by 7MB and its never
> released.
> This ends up with an OutOfMemoryError caused by Metaspace every 15 days and i
> need to restart the cluster to clean the metaspace
> taskmanager.memory.jvm-metaspace.size is set to 512mb
> Any idea of what could be causing this metaspace grow and why is it not
> released ?
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
