Vladimir Steshin created IGNITE-28996:
-----------------------------------------
Summary: 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
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 `IgniteThreadPoolExecutor` to the Idle Verify.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
