[ https://issues.apache.org/jira/browse/SOLR-8500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135896#comment-15135896 ]
Erick Erickson commented on SOLR-8500: -------------------------------------- NOTE: This is an "expert" level operation, see the CHANGES.txt entry, reproduced here: this is an expert option and can result in more often needing to do full index replication for recovery, the sweet spot for using this is very high volume, leader-only indexing. > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org