[jira] [Commented] (FLINK-4094) Off heap memory deallocation might not properly work

["ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-4094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397634#comment-15397634 ] 

ramkrishna.s.vasudevan commented on FLINK-4094:
-----------------------------------------------

Can I work on this? I saw the code - if preallocation is false and the memory type is OFFHEAP we should not be allowing that config. May be we can even disallow that combination or if OFFHEAP is the type we will always allow preallocation. Or add our own internal offheap buffer management that is not exposed to user? May be that is redundant.
Not allowing preallocation and creating offheap buffers is very dangerous.

> 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
>            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)