[ 
https://issues.apache.org/jira/browse/FLINK-15989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Zagrebin closed FLINK-15989.
-----------------------------------
    Resolution: Fixed

merged into master by a7521844d7a120b2e36dd7d57cea0fe5d819dbba
merged into 1.10 by 25ec89b8dae175246fd28972f8dbf7d479e89b5f

> Rewrap OutOfMemoryError in allocateUnpooledOffHeap with better message
> ----------------------------------------------------------------------
>
>                 Key: FLINK-15989
>                 URL: https://issues.apache.org/jira/browse/FLINK-15989
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>            Reporter: Andrey Zagrebin
>            Assignee: Andrey Zagrebin
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.1, 1.11.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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)

Reply via email to