[
https://issues.apache.org/jira/browse/SOLR-6816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241199#comment-14241199
]
Per Steffensen commented on SOLR-6816:
--------------------------------------
Make sure to document when it is safe to turn off the version-check for replica
(overwrite=false). Believe the version-check is also used to detect and prevent
old versions that get to the replica last does not overwrite new versions that
get to the replica first. E.g leader might get an update-request of document D
updating it from state S1 to S2, and send a request U1 to a replica with
overwrite=false saying "just write S2 without checking". Immediately after the
update of D from S1 to S2, the leader gets another request updating it from S2
to S3. Leader again reacts by sending a "just write S3 without
checking"-request U2 to the replica. The replica might receive U2 before U1 (if
replica-request is not sent and waited for response while the leader has the
bucket-lock for the document) and then you are in trouble.
Sure that is an odd case, just do not forget that versions are also used for
that on replica (AFAIK)
> Review SolrCloud Indexing Performance.
> --------------------------------------
>
> Key: SOLR-6816
> URL: https://issues.apache.org/jira/browse/SOLR-6816
> Project: Solr
> Issue Type: Task
> Components: SolrCloud
> Reporter: Mark Miller
> Priority: Critical
> Attachments: SolrBench.pdf
>
>
> We have never really focused on indexing performance, just correctness and
> low hanging fruit. We need to vet the performance and try to address any
> holes.
> Note: A common report is that adding any replication is very slow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
