[
https://issues.apache.org/jira/browse/ARROW-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438507#comment-16438507
]
ASF GitHub Bot commented on ARROW-2458:
---------------------------------------
robertnishihara commented on issue #1893: ARROW-2458: [Plasma] Use one thread
pool per PlasmaClient
URL: https://github.com/apache/arrow/pull/1893#issuecomment-381361348
Ah, the issue is that the current usage of the global thread pool variable
is not thread safe, so if two clients in the same process try to `Seal` an
object at the same time, it can segfault.
This fixes that issue.
I agree that there's no reason to preserve a detrimental behavior (I brought
that up because we may need to solve the problem in a different way down the
road since it will still exist for multiple processes).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [Plasma] PlasmaClient uses global variable
> ------------------------------------------
>
> Key: ARROW-2458
> URL: https://issues.apache.org/jira/browse/ARROW-2458
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Plasma (C++)
> Affects Versions: 0.9.0
> Reporter: Philipp Moritz
> Assignee: Philipp Moritz
> Priority: Major
> Labels: pull-request-available
>
> The threadpool threadpool_ that PlasmaClient is using is global at the
> moment. This prevents us from using multiple PlasmaClients in the same
> process (one per thread).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
