[
https://issues.apache.org/jira/browse/FLINK-8809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416137#comment-16416137
]
Greg Hogan commented on FLINK-8809:
-----------------------------------
Will a restricted {{MaxDirectMemorySize}} prevent an OOME? If this is a
production issue may want to document use of {{jdk.nio.maxCachedBufferSize}}
which would prevent the JVM from retaining large "temporary" buffers (some
discussion [here|http://www.evanjones.ca/java-bytebuffer-leak.html], and note
that the option is available from
[jdk8u102|http://www.oracle.com/technetwork/java/javase/8u102-relnotes-3021767.html]).
> 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: TaskManager
> 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
(v7.6.3#76005)
