[
https://issues.apache.org/jira/browse/SOLR-8500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120152#comment-15120152
]
Erick Erickson commented on SOLR-8500:
--------------------------------------
First let me say I have only the most cursory understanding of "the reordering
problem". My assumption is that since CUSC is batching up sub-lists of the
update set and sending them in parallel that if doc1 is followed by doc2 in the
original list, doc2 might get to the indexing node before doc1, be it an
update, delete, add, whatever.
That said, I don't really understand how reordering matters if (as per the
original problem statement), it's _guaranteed_ that each document is new and is
submitted exactly once _ever_. I guess another important restriction is that
the client doesn't care if docs get into the index in a different order than
they were sent. How would correctness be threatened in that situation?
If the concern is that this is a too-specialized use-case that allows people to
set it and shoot themselves in the foot too easily, that's a point. I just
don't get why, in this specific use-case, this is a correctness question.
All that said, if Yonik's fingerprint stuff is going in relatively soon, it's
probably all moot and we can just wait on this...
> 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]
