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 2026/01/15 12:04:00 UTC

[jira] [Resolved] (IGNITE-22687) Do not use common system thread pool in SQL

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

Roman Puchkovskiy resolved IGNITE-22687.
----------------------------------------
    Resolution: Duplicate

Fixed by IGNITE-24477

> Do not use common system thread pool in SQL
> -------------------------------------------
>
>                 Key: IGNITE-22687
>                 URL: https://issues.apache.org/jira/browse/IGNITE-22687
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Roman Puchkovskiy
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain, ignite-3
>
> Currently, IgniteSqlImpl#processCursor() has the following line:
> cursor.nextResult().whenCompleteAsync(this::processCursor);
> This schedules subsequent processCursor() invocation to be executed in the system common ForkJoinPool, which is dangerous because the pool might bee exhausted (starved) by the user, and SQL execution could suffer.
> It is suggested to use some Ignite-internal thread pool here.



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