[
https://issues.apache.org/jira/browse/SOLR-6816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384600#comment-14384600
]
Yonik Seeley commented on SOLR-6816:
------------------------------------
bq. boolean updated = getUpdatedDocument(cmd, versionOnUpdate);
That's for atomic udpates... and the version passed is the version that was on
the update itself, not the version of the last doc in the index.
It will be interesting to see if the code works w/o any tweaks... it's been
sitting there since the beginning of solrcloud, for years unused and untested
;-)
{code}
// if we aren't the leader, then we need to check that updates were
not re-ordered
if (bucketVersion != 0 && bucketVersion < versionOnUpdate) {
// we're OK... this update has a version higher than anything
we've seen
// in this bucket so far, so we know that no reordering has yet
occurred.
bucket.updateHighest(versionOnUpdate);
{code}
> 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]
