[
https://issues.apache.org/jira/browse/SOLR-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163992#comment-14163992
]
Erick Erickson commented on SOLR-6606:
--------------------------------------
I admit I don't know the code well (at all, really). What I wonder is whether
we can _really_ count on all the segments being aligned. 'cause if there's any
chance at all that segment 1 on any node has different docs than segment 1 on
any other node, then it seems like things aren't going to work. So can we
really guarantee that the segments are identical for all members of a slice
under this scenario?
That said, it would be really cool to not have to replicate the entire index
when synching....
> In cloud mode the leader should distribute autoCommits to it's replicas
> -----------------------------------------------------------------------
>
> Key: SOLR-6606
> URL: https://issues.apache.org/jira/browse/SOLR-6606
> Project: Solr
> Issue Type: Improvement
> Reporter: Varun Thacker
> Fix For: 5.0, Trunk
>
> Attachments: SOLR-6606.patch
>
>
> Today in SolrCloud different replicas of a shard can trigger auto (hard)
> commits at different times. Although the documents which get added to the
> system remain consistent the way the segments gets formed can be different
> because of this.
> The downside of segments not getting formed in an identical fashion across
> replicas is that when a replica goes into recovery chances are that it has to
> do a full index replication from the leader. This is time consuming and we
> can possibly avoid this if the leader forwards auto (hard) commit commands to
> it's replicas and the replicas never explicitly trigger an auto (hard) commit.
> I am working on a patch. Should have it up shortly
--
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
