You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Philipp Moritz (JIRA)" <ji...@apache.org> on 2019/07/16 07:32:00 UTC

[jira] [Resolved] (ARROW-5560) Cannot create Plasma object after OutOfMemory error

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

Philipp Moritz resolved ARROW-5560.
-----------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 0.13.0)
                   0.14.1

Issue resolved by pull request 4850
[https://github.com/apache/arrow/pull/4850]

> Cannot create Plasma object after OutOfMemory error
> ---------------------------------------------------
>
>                 Key: ARROW-5560
>                 URL: https://issues.apache.org/jira/browse/ARROW-5560
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: C++ - Plasma
>    Affects Versions: 0.13.0
>            Reporter: Stephanie Wang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.14.1
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> If the client tries to call `CreateObject` and there is not enough memory left in the object store to create it, an `OutOfMemory` error will be returned. However, the plasma store also creates an entry for the object, even though it failed to be created. This means that later on, if the client tries to create the object again, it will receive an error that the object already exists. Also, if the client tries to get the object, it will hang because the entry appears to be unsealed.
> We should fix this by only creating the object entry if the `CreateObject` operation succeeds.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)