[jira] [Commented] (ARROW-1084) Implementations of BufferAllocator should handle Netty's OutOfDirectMemoryError

["Julien Le Dem (JIRA)" <ji...@apache.org>]

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

Julien Le Dem commented on ARROW-1084:
--------------------------------------

merged in https://github.com/apache/arrow/commit/ba97f343f631138a51a1c337eebba83e03add454

> Implementations of BufferAllocator should handle Netty's OutOfDirectMemoryError
> -------------------------------------------------------------------------------
>
>                 Key: ARROW-1084
>                 URL: https://issues.apache.org/jira/browse/ARROW-1084
>             Project: Apache Arrow
>          Issue Type: Task
>          Components: Java - Memory
>            Reporter: Deneche A. Hakim
>            Assignee: Deneche A. Hakim
>            Priority: Minor
>             Fix For: 0.5.0
>
>
> Implementations of BufferAllocator.buffer(...) are expected to throw an OutOfMemoryException if the buffer cannot be allocated. There are multiple reasons for that:
> - allocator exceeded it's memory limit
> - Netty exceeded it's direct memory limit
> - the System is unable to fulfill Netty's request for more direct memory
> For now only the first case throws an OutOfMemoryException. The second throws an OutOfDirectMemoryError, and the third an OutOfMemoryError with the "Direct buffer memory" error message.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)