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/01/31 11:19:00 UTC

[jira] [Closed] (FLINK-8809) Decrease maximum value of DirectMemory at default config

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

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

Should no longer be a problem with FLIP-49.

> Decrease maximum value of DirectMemory at default config
> --------------------------------------------------------
>
>                 Key: FLINK-8809
>                 URL: https://issues.apache.org/jira/browse/FLINK-8809
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>            Reporter: Kirill A. Korinskiy
>            Priority: Major
>
> Good day!
>  
> Have I can see since this [commit|https://github.com/apache/flink/commit/6c44d93d0a9da725ef8b1ad2a94889f79321db73] TaskManager uses 8,388,607 terabytes as maximum out of heap memory. I guess that not any system has so much memory and it may be a reason to kill java process by OOM Killer.
>  
> I suggest to decrease this value to reasonable value by default.
>  
> Right now I see only one way to overstep this hardcoded value: setup FLINK_TM_HEAP to 0, and specified heap size by hand over FLINK_ENV_JAVA_OPTS_TM. 
> Thanks



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