You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2026/08/21 08:08:00 UTC

[jira] [Commented] (IGNITE-28996) Idle Verify utility shouldn't use Java's ForkJoinPool

    [ https://issues.apache.org/jira/browse/IGNITE-28996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18106526#comment-18106526 ] 

Ignite TC Bot commented on IGNITE-28996:
----------------------------------------

{panel:title=Branch: [pull/13494/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13494/head] Base: [master] : No new tests found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9297863&amp;buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9297863 rerunBuildIds=9299223{color}

> Idle Verify utility shouldn't use Java's ForkJoinPool
> -----------------------------------------------------
>
>                 Key: IGNITE-28996
>                 URL: https://issues.apache.org/jira/browse/IGNITE-28996
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladimir Steshin
>            Priority: Major
>              Labels: ise
>          Time Spent: 5.5h
>  Remaining Estimate: 0h
>
> In the Idle Verify we use `ForkJoinPool#commonPool()`. It is unusual in Ignite. FJP is engaged in few places. Normally, we allocate own thread pools, task executors like `IgniteThreadPoolExecutor`. Also, `ForkJoinPool#commonPool()` consumes all the visible CPUs - 1 by default. That size is controversial. And we have no typical setting of idle verify threads number. The suggestion is to set Ignite's or just other thread pool/executor to the Idle Verify.



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