[
https://issues.apache.org/jira/browse/IGNITE-22933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtsev updated IGNITE-22933:
-----------------------------------------
Description:
Our codebase contains some call to the {{ThreadPoolExecutor}} constructor with
the following parameters:
```
new ThreadPoolExecutor(
0,
<some_value>,
<some_value>,
<some_value>,
new LinkedBlockingQueue<>(),
<some_value>
)
```
The combination of "maxCorePoolSize" being equal to 0 and an unbounded queue
actually means that all tasks submitted to this thread pool will be executed
sequentially due to the internal behavior of {{ThreadPoolExecutor}}.
All such places must be replaced with more sensible values, like a non-zero
{{corePoolSize}} and {{allowCoreThreadTimeOut}} set to {{true}}.
> Replace ThreadPoolExecutors with a corePoolSize equal to 0
> ----------------------------------------------------------
>
> Key: IGNITE-22933
> URL: https://issues.apache.org/jira/browse/IGNITE-22933
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksandr Polovtsev
> Priority: Major
> Labels: ignite-3
>
> Our codebase contains some call to the {{ThreadPoolExecutor}} constructor
> with the following parameters:
> ```
> new ThreadPoolExecutor(
> 0,
> <some_value>,
> <some_value>,
> <some_value>,
> new LinkedBlockingQueue<>(),
> <some_value>
> )
> ```
> The combination of "maxCorePoolSize" being equal to 0 and an unbounded queue
> actually means that all tasks submitted to this thread pool will be executed
> sequentially due to the internal behavior of {{ThreadPoolExecutor}}.
> All such places must be replaced with more sensible values, like a non-zero
> {{corePoolSize}} and {{allowCoreThreadTimeOut}} set to {{true}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
