[
https://issues.apache.org/jira/browse/FLINK-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16735628#comment-16735628
]
Daniel Harper edited comment on FLINK-10317 at 1/7/19 10:09 AM:
----------------------------------------------------------------
(colleague of [~nawaidshamim] here)
Launched the job with -X:MetaSpaceSize=180M and left the job to run a bit,
killing one of the task managers to force a job restart every 2 minutes
Once the metaspace reached 180M the task manager died with the error:
{code}
java.lang.OutOfMemoryError: Metaspace
{code}
which suggests to me the GC is unable to mark much eligible for collection and
simply hits the limit and dies.
!Screen Shot 2019-01-07 at 10.08.47.png!width=400px!
!Screen Shot 2019-01-07 at 10.08.39.png!width=400px!
was (Author: djharper):
(colleague of [~nawaidshamim] here)
Launched the job with -X:MetaSpaceSize=180M and left the job to run a bit,
killing one of the task managers to force a job restart every 2 minutes
Once the metaspace reached 180M the task manager died with the error:
{code}
java.lang.OutOfMemoryError: Metaspace
{code}
which suggests to me the GC is unable to mark much eligible for collection and
simply hits the limit and dies.
!Screen Shot 2019-01-07 at 10.08.47.png!
!Screen Shot 2019-01-07 at 10.08.39.png!
> 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: Screen Shot 2019-01-07 at 10.08.39.png, Screen Shot
> 2019-01-07 at 10.08.47.png, 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)
