[
https://issues.apache.org/jira/browse/IGNITE-28996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-28996:
--------------------------------------
Labels: ise (was: )
> 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: 4h 10m
> 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)
