You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jingsong Lee (Jira)" <ji...@apache.org> on 2020/02/11 10:02:00 UTC
[jira] [Commented] (FLINK-15989) Rewrap OutOfMemoryError in
allocateUnpooledOffHeap with better message
[ https://issues.apache.org/jira/browse/FLINK-15989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034314#comment-17034314 ]
Jingsong Lee commented on FLINK-15989:
--------------------------------------
Thanks [~azagrebin], yes, we can improve this message too.
> Rewrap OutOfMemoryError in allocateUnpooledOffHeap with better message
> ----------------------------------------------------------------------
>
> Key: FLINK-15989
> URL: https://issues.apache.org/jira/browse/FLINK-15989
> Project: Flink
> Issue Type: Improvement
> Reporter: Andrey Zagrebin
> Priority: Major
> Fix For: 1.10.1, 1.11.0
>
>
> Now if Flink allocates direct memory in MemorySegmentFactory#allocateUnpooledOffHeapMemory and its limit is exceeded for any reason, e.g. user code over-allocated direct memory, ByteBuffer#allocateDirect will throw a generic "OutOfMemoryError: Direct buffer memory". We can catch it and add a message which provides more explanation and points to an option taskmanager.memory.task.off-heap.size to increase as a possible solution.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)