[
https://issues.apache.org/jira/browse/IGNITE-12684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17047267#comment-17047267
]
Kirill Tkalenko commented on IGNITE-12684:
------------------------------------------
[~mmuzaf] thank you, you are right, I tried locally and it turned out that only
1 thread works.
> Optimize count of threads for rebuild indexes
> ---------------------------------------------
>
> Key: IGNITE-12684
> URL: https://issues.apache.org/jira/browse/IGNITE-12684
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Major
> Fix For: 2.9
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We were recently implemented the new property
> {{INDEX_REBUILDING_PARALLELISM}} (by issue IGNITE-11979).
> That fix do possible to rebuild indexes, after restart without index.bin or
> restore from snapshot to another topology, in parallel threads.
> But now the process of rebuild can to consume a lot of threads, which limited
> on INDEX_REBUILDING_PARALLELISM * AVAILABLE_PROC_CNT (count of thread in
> public pool).
> For example in case of INDEX_REBUILDING_PARALLELISM = 28 and 64 CPU it will
> be more then 1.5К threads.
> Look at the method, it will create dedicate thread on each invocation
> `org.apache.ignite.internal.processors.query.schema.SchemaIndexCacheVisitorImpl#processPartitionsAsync`
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
