[
https://issues.apache.org/jira/browse/IGNITE-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037088#comment-17037088
]
Ilya Kasnacheev commented on IGNITE-12663:
------------------------------------------
[~agura] Actually, Idea is very awful at presenting thread dumps. You can't
search threads by name, and it keeps resetting your select to first thread. And
the default JVM thread dump just dumps them all to console, without any
filtering. In Idea you can't even save program output to file. It's unusable
currently.
I have faced the rebalance thread pool issue - it's 4 by default, and system
pool has to be bigger. This makes the change almost useless, but I will still
take a look where we can get it to.
> Let's limit all thread pools' sizes to 3 in tests
> -------------------------------------------------
>
> Key: IGNITE-12663
> URL: https://issues.apache.org/jira/browse/IGNITE-12663
> Project: Ignite
> Issue Type: Test
> Reporter: Ilya Kasnacheev
> Assignee: Ilya Kasnacheev
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The rationale is, it is very painful shoving through thread dumps of test
> with N CPU threads in every pool.
> Why 3? It should allow all kinds of race conditions to still happen. Of
> course, we should allow specific tests to override this value.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
