[
https://issues.apache.org/jira/browse/SOLR-8500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated SOLR-8500:
---------------------------------
Summary: Allow the number of threads ConcurrentUpdateSolrClient
StreamingSolrClients configurable by a system property (was: Allow the number
of threds ConcurrentUpdateSolrClient StreamingSolrClients configurable by a
system property)
> 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
