[
https://issues.apache.org/jira/browse/IGNITE-28996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18106740#comment-18106740
]
Ignite TC Bot commented on IGNITE-28996:
----------------------------------------
The required documentation update is already included in the merged
implementation PR https://github.com/apache/ignite/pull/13494. The PR updates
docs/_docs/tools/control-script.adoc to describe the dedicated idle_verify
utility thread pool, the default size, the IGNITE_IDLE_VERIFY_POOL_SIZE system
property, thread expiry, and consistency repair sharing the same pool. Removing
Docs Required and preserving Release Notes Required.
> 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
> Assignee: Vladimir Steshin
> Priority: Major
> Labels: ise
> Fix For: 2.19
>
> Time Spent: 5h 40m
> 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)
