You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/02/15 06:47:00 UTC

[jira] [Resolved] (IMPALA-6519) Allow atomic allocation of an unreserved buffer

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

Tim Armstrong resolved IMPALA-6519.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.12.0
                   Impala 3.0

> Allow atomic allocation of an unreserved buffer
> -----------------------------------------------
>
>                 Key: IMPALA-6519
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6519
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>            Priority: Major
>              Labels: resource-management
>             Fix For: Impala 3.0, Impala 2.12.0
>
>
> [~kwho] needs this for his KRPC work. We want the exchange node to allocate buffer pool buffers to store incoming data. However, the current interface doesn't easily allow multiple threads to allocate buffers for which they don't have reservations. Generally allocating buffers without having a reservation would be an anti-pattern but it is a useful transitional mechanism until we can reserve memory for the exchange node.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)