[
https://issues.apache.org/jira/browse/SOLR-8500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106132#comment-15106132
]
Erick Erickson commented on SOLR-8500:
--------------------------------------
bq: I think using more than 1 thread may actually introduce more reordering
problems right now.
Does it matter in the case that I outlined? That there are no updates to
existing documents to contend with so even if docs get reordered it shouldn't
have any effects noticeably by the end user.
Or am I missing the boat?
> Allow the number of threads ConcurrentUpdateSolrClient StreamingSolrClients
> configurable by a system property
> -------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-8500
> URL: https://issues.apache.org/jira/browse/SOLR-8500
> Project: Solr
> Issue Type: Improvement
> Reporter: Erick Erickson
> Priority: Minor
> Attachments: SOLR-8500.patch
>
>
> Despite the warning in that code, in extremely high throughput situations
> where there are guaranteed to be no updates to existing documents, it can be
> useful to have more than one runner.
> I envision this as an "expert" kind of thing, used only in situations where
> the a-priori knowledge is that there are no updates to existing documents.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
