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

Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2024/06/13 14:39:00 UTC

[jira] [Updated] (IGNITE-22503) AsyncFileIo should use an Ignite thread pool instead of the system one

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

Roman Puchkovskiy updated IGNITE-22503:
---------------------------------------
    Description: 
AsyncFileIo opens the channel like this:

ch = AsynchronousFileChannel.open(filePath, modes);

As a result, the channel uses the system default thread pool. We need to supply our own pool, one pool per storage instance (so per storage profile).

> AsyncFileIo should use an Ignite thread pool instead of the system one
> ----------------------------------------------------------------------
>
>                 Key: IGNITE-22503
>                 URL: https://issues.apache.org/jira/browse/IGNITE-22503
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>
> AsyncFileIo opens the channel like this:
> ch = AsynchronousFileChannel.open(filePath, modes);
> As a result, the channel uses the system default thread pool. We need to supply our own pool, one pool per storage instance (so per storage profile).



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