[
https://issues.apache.org/jira/browse/ARROW-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17662426#comment-17662426
]
Rok Mihevc commented on ARROW-5402:
-----------------------------------
This issue has been migrated to [issue
#16741|https://github.com/apache/arrow/issues/16741] on GitHub. Please see the
[migration documentation|https://github.com/apache/arrow/issues/14542] for
further details.
> [Plasma] Pin objects in plasma store
> ------------------------------------
>
> Key: ARROW-5402
> URL: https://issues.apache.org/jira/browse/ARROW-5402
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++ - Plasma
> Reporter: Zhijun Fu
> Assignee: Zhijun Fu
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> [https://github.com/apache/arrow/issues/4368]
> Sometimes we want to "pin" an object in plasma store - we don't want this
> object to be deleted even though there's nobody that's currently referencing
> it. In this case, we can specify a flag when creating the object so that it
> won't be deleted by LRU cache when its refcnt drops to 0, and can only be
> deleted by an explicit {{Delete()}} call.
> Currently, we found that an actor FO problem. The actor creation task depends
> on a plasma object put by user. After the the actor running for a long time,
> the object will be deleted by plasma LRU. Then, an Actor FO happens, the
> creation task cannot find the object put by user, so the FO is hanging
> forever.
> Would this make sense to you?
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
