You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Deneche A. Hakim (JIRA)" <ji...@apache.org> on 2017/06/02 17:11:04 UTC

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

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

Deneche A. Hakim updated ARROW-1084:
------------------------------------
    Description: 
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.


  was:
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 enable 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.



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