[
https://issues.apache.org/jira/browse/FLINK-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725939#comment-16725939
]
Nico Kruber commented on FLINK-10317:
-------------------------------------
Actually limiting metaspace will also trigger its garbage collection (without
limit it won't do GC for the metaspace!).
Did you test this out with the metaspace limit?
If setting metaspace correctly (please verify in the TM logs) does not help,
then your issue should be continued in a separate thread like FLINK-9080 or
FLINK-11205.
> Configure Metaspace size by default
> -----------------------------------
>
> Key: FLINK-10317
> URL: https://issues.apache.org/jira/browse/FLINK-10317
> Project: Flink
> Issue Type: Bug
> Components: Startup Shell Scripts
> Affects Versions: 1.5.3, 1.6.0, 1.7.0
> Reporter: Stephan Ewen
> Assignee: vinoyang
> Priority: Major
> Fix For: 1.6.4, 1.7.2, 1.8.0
>
> Attachments: Screenshot 2018-12-18 at 12.14.11.png
>
>
> We should set the size of the JVM Metaspace to a sane default, like
> {{-XX:MaxMetaspaceSize=256m}}.
> If not set, the JVM offheap memory will grow indefinitely with repeated
> classloading and Jitting, eventually exceeding allowed memory on docker/yarn
> or similar setups.
> It is hard to come up with a good default, however, I believe the error
> messages one gets when metaspace is too small are easy to understand (and
> easy to take action), while it is very hard to figure out why the memory
> footprint keeps growing steadily and infinitely.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
