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

Posted to jira@arrow.apache.org by "Antoine Pitrou (Jira)" <ji...@apache.org> on 2022/11/23 16:16:00 UTC

[jira] [Resolved] (ARROW-18383) [C++] Avoid global variables for thread pools and at-fork handlers

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

Antoine Pitrou resolved ARROW-18383.
------------------------------------
    Resolution: Fixed

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

> [C++] Avoid global variables for thread pools and at-fork handlers
> ------------------------------------------------------------------
>
>                 Key: ARROW-18383
>                 URL: https://issues.apache.org/jira/browse/ARROW-18383
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: C++
>            Reporter: Antoine Pitrou
>            Assignee: Antoine Pitrou
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 11.0.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Investigation revealed an issue where the global IO thread pool could be constructed before the at-fork handler internal state. The IO thread pool, created on library load, would register an at-fork handler; then, the at-fork handler state would be initialized and clobber the handler registered just before.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)