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 2020/11/06 10:43:00 UTC

[jira] [Closed] (FLINK-16278) Document new settings for MaxMetaSpace in 1.10

     [ https://issues.apache.org/jira/browse/FLINK-16278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann closed FLINK-16278.
---------------------------------
    Resolution: Not A Problem

Memory settings have been documented.

> Document new settings for MaxMetaSpace in 1.10
> ----------------------------------------------
>
>                 Key: FLINK-16278
>                 URL: https://issues.apache.org/jira/browse/FLINK-16278
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation, Runtime / Coordination
>    Affects Versions: 1.10.0
>            Reporter: None none
>            Priority: Major
>
> I was running Flink 1.8 and decided to upgrade to 1.10. I started to get OutOfMemory: Metaspace on Task nodes and they would shutdown.
> Deploying 3-4 jobs was ok, deploying 5th job, the task manager would shutdown after a couple of minutes.
> Some investigation shows, that the Flink startup scripts set this to 100m.
> Setting taskmanager.memory.jvm-metaspace.size: 256m seems to alleviate the problem. Looking at the docs, this setting seems new. But it is not documented anywhere that the default is now 100m
> I would like to add the exact same setup/jobs on Flink 1.8 was working fine.
> [Here|http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/MaxMetaspace-default-may-be-to-low-td33049.html] is a conversation on the mailing list as well.
> I think the upgrade/migration docs should indicate this and also maybe the default size.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)