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

Chesnay Schepler closed FLINK-18190.
------------------------------------
    Fix Version/s:     (was: 1.11.0)
       Resolution: Not A Problem

Naturally, if the Flink Memory is fixed then a change in Metaspace must affect 
overhead. That things behave differently if Flink Memory is not fixed makes 
sense.

> Document implications on derived memory values when configuring meta space
> --------------------------------------------------------------------------
>
>                 Key: FLINK-18190
>                 URL: https://issues.apache.org/jira/browse/FLINK-18190
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Chesnay Schepler
>            Priority: Major
>
> Let's start with a base line, where we configure the total process memory to 
> 1024mb:
> {code}
> Final Master Memory configuration:
>   Total Process Memory:      1024.000mb (1073741824 bytes)
>     Total Flink Memory:      576.000mb (603979776 bytes)
>       Flink Heap Memory:     448.000mb (469762048 bytes)
>       Flink Off-heap Memory: 128.000mb (134217728 bytes)
>     JVM Metaspace Memory:    256.000mb (268435456 bytes)
>     JVM Overhead Memory:     192.000mb (201326592 bytes)
> {code}
> Increasing the Metaspace Memory by 1 reduces the Total Flink memory:
> {code}
> Final Master Memory configuration:
>   Total Process Memory:      1024.000mb (1073741824 bytes)
>     Total Flink Memory:      575.000mb (602931200 bytes)
>       Flink Heap Memory:     447.000mb (468713472 bytes)
>       Flink Off-heap Memory: 128.000mb (134217728 bytes)
>     JVM Metaspace Memory:    257.000mb (269484032 bytes)
>     JVM Overhead Memory:     192.000mb (201326592 bytes)
> {code}
> If on the other hand we configured the Total Flink Memory as well, then the 
> JVM Overhead is reduced instead.
> This is somewhat in line with the documentation, but it may be good to 
> explicitly document this behavior. Users that rely on the default 
> configuration may stumble on this when they run into metaspace issues, 
> increasing this one option without having configured anything else.



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

Reply via email to