[
https://issues.apache.org/jira/browse/FLINK-4094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408274#comment-15408274
]
ramkrishna.s.vasudevan commented on FLINK-4094:
-----------------------------------------------
I created the log related msg and the doc. So what info should we give in the
doc. Will the following be enough?
{code}
+- `taskmanager.memory.preallocate`: Can be either of `true` or `false`.
Specifies whether task managers should allocate all managed memory when
starting up. (DEFAULT: false). When `taskmanager.memory.off-heap` is set to
`true`, then it is advised that this configuration is also set to `true`,
because when set to
+`false`, cleaning up of the allocated offheap memory kicks up only when the
configured JVM parameter MaxDirectMemorySize is reached by triggering a full GC.
{code}
I can submit a PR after this.
bq.If a task requests more memory than the system is configured for, it will
throw an error.
Thanks [~StephanEwen].
> Off heap memory deallocation might not properly work
> ----------------------------------------------------
>
> Key: FLINK-4094
> URL: https://issues.apache.org/jira/browse/FLINK-4094
> Project: Flink
> Issue Type: Bug
> Components: Local Runtime
> Affects Versions: 1.1.0
> Reporter: Till Rohrmann
> Assignee: ramkrishna.s.vasudevan
> Priority: Critical
> Fix For: 1.1.0
>
>
> A user reported that off-heap memory is not properly deallocated when setting
> {{taskmanager.memory.preallocate:false}} (per default) [1]. This can cause
> the TaskManager process being killed by the OS.
> It should be possible to execute multiple batch jobs with preallocation
> turned off. No longer used direct memory buffers should be properly garbage
> collected so that the JVM process does not exceed it's maximum memory bounds.
> [1]
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/offheap-memory-allocation-and-memory-leak-bug-td12154.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
