flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4094) Off heap memory deallocation might not properly work
Date Mon, 20 Jun 2016 10:51:05 GMT

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

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

Offheap direct memory cannot be cleared unless a full GC happens. If the allocated memory
happens to be in the active working set always (like this preallocate does) then there is
always the chance of reusing the existing allocated direct memory and things should be fine.


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

Mime
View raw message