[
https://issues.apache.org/jira/browse/SOLR-8500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135895#comment-15135895
]
ASF subversion and git services commented on SOLR-8500:
-------------------------------------------------------
Commit 129f7153087b279908d6340e7f8a5b024f0f7cad in lucene-solr's branch
refs/heads/branch_5x from [~erickerickson]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=129f715 ]
SOLR-8500: Allow the number of threads ConcurrentUpdateSolrClient
StreamingSolrClients configurable by a system property
(cherry picked from commit 3e7fe7867f64b254680d462092d01f07858aa7c3)
Conflicts:
solr/CHANGES.txt
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
