You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2016/01/07 02:11:39 UTC
[jira] [Created] (SOLR-8500) Allow the number of threds
ConcurrentUpdateSolrClient StreamingSolrClients configurable by a system
property
Erick Erickson created SOLR-8500:
------------------------------------
Summary: Allow the number of threds 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
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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org