[
https://issues.apache.org/jira/browse/LUCENE-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986108#comment-14986108
]
Brandon Mintern commented on LUCENE-6659:
-----------------------------------------
We just upgraded from 5.2.1 to 5.3.1, and none of the intermediate change logs
seem to mention this change.
We were previously using IndexWriterConfig#setMaxThreadStates to allow us to
configure the number of threads that can write to the index at the same time.
Looking at the source, it used to construct a new DocumentsWriterPerThreadPool
instance and setting it.
Unfortunately, setIndexerThreadPool has package visibility, and besides, that
constructor has been removed from DocumentsWriterPerThreadPool.
Were we mistaken in our understanding of the purpose of this method? Going
forward, how can we be limit the number of threads that can write to an index?
> Remove IndexWriterConfig.get/setMaxThreadStates
> -----------------------------------------------
>
> Key: LUCENE-6659
> URL: https://issues.apache.org/jira/browse/LUCENE-6659
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 5.3, Trunk
>
> Attachments: LUCENE-6659.patch
>
>
> Ever since LUCENE-5644, IndexWriter will aggressively reuse its internal
> thread states across threads, whenever one is free.
> I think this means we can safely remove the sneaky maxThreadStates limit
> (default 8) that we have today: IW will only ever allocate as many thread
> states as there are actual concurrent threads running through it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
