[
https://issues.apache.org/jira/browse/IGNITE-20165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-20165:
-----------------------------------------
Description: JRaft uses a bunch of thread pools to execute its operations.
Most of these thread pools use the number of CPUs to determine the amount of
threads they can use. For example, as described in IGNITE-20080, having 64
cores led to JRaft allocating around 600 threads. Even though these thread
pools are shared between all Raft nodes, this approach is clearly sub-optimal,
because it should take into account both the amount of nodes as well as the
number of processors. It may also be beneficial to revise the amount of thread
pools used and why they are needed and reduce their number, if possible.
> Revisit the configuration of thread pools used by JRaft
> -------------------------------------------------------
>
> Key: IGNITE-20165
> URL: https://issues.apache.org/jira/browse/IGNITE-20165
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksandr Polovtcev
> Priority: Major
> Labels: ignite-3
>
> JRaft uses a bunch of thread pools to execute its operations. Most of these
> thread pools use the number of CPUs to determine the amount of threads they
> can use. For example, as described in IGNITE-20080, having 64 cores led to
> JRaft allocating around 600 threads. Even though these thread pools are
> shared between all Raft nodes, this approach is clearly sub-optimal, because
> it should take into account both the amount of nodes as well as the number of
> processors. It may also be beneficial to revise the amount of thread pools
> used and why they are needed and reduce their number, if possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
