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/02/06 18:59:39 UTC

[jira] [Resolved] (SOLR-8500) Allow the number of threads ConcurrentUpdateSolrClient StreamingSolrClients configurable by a system property

     [ https://issues.apache.org/jira/browse/SOLR-8500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Erick Erickson resolved SOLR-8500.
----------------------------------
       Resolution: Fixed
    Fix Version/s: Trunk
                   5.5

> 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
>            Assignee: Erick Erickson
>            Priority: Minor
>             Fix For: 5.5, Trunk
>
>         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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org