You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Rok Mihevc (Jira)" <ji...@apache.org> on 2023/01/11 07:13: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 ]

Rok Mihevc updated ARROW-1084:
------------------------------
    External issue URL: https://github.com/apache/arrow/issues/16672

> 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
>            Reporter: Abdel Hakim Deneche
>            Assignee: Abdel Hakim Deneche
>            Priority: Minor
>             Fix For: 0.4.1
>
>
> 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
(v8.20.10#820010)