-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
None
-
Affects Version/s: 5.7, 5.6.6, 5.8
-
Component/s: Documentation - All
In the page: https://confluence.atlassian.com/display/DOC/Recognised+System+Properties we've got:
index.queue.thread.count 3.3 See "Effect" Confluence Sets the number of threads to be used for the reindex job. The value has to be in the range of 1 to 10 (inclusive), i.e. at least one thread but no more than 10 threads will be used. There is no default value, i.e. If you don't set index.queue.thread.count, the number of threads to be used are calculated based on the number of objects that need to be reindexed and the number of processors available (a maximum of 10 threads will be used). If you set index.queue.thread.count=2, then two threads will be used to reindex the content (regardless of the number of objects to be reindexed or the number of processors available) If you set index.queue.thread.count=200, then ten threads (the maximum allowed) will be used to reindex the content.
The current maximum is 50 instead of 10 in the newer version.
- relates to
-
CONFSERVER-30671 Indexer threads exceed maximum of 10 during space import
-
- Closed
-
-
CONFSERVER-37394 Number of the Threads for Indexing Should be Increased
- Closed