[ 
https://issues.apache.org/jira/browse/SOLR-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169142#comment-14169142
 ] 

Ferenczi Jim commented on SOLR-6606:
------------------------------------

Is is intended for partial recovery or only to distribute the downloads on a 
full recovery (when the Replica downloads a full index from the master) ? I am 
saying this because for the partial recovery you need to handle the deletes as 
well. For instance if one replica missed the last commit he could download the 
segment from the master but he would loose all the deletes related to this 
update. Keeping the list of every delete per commit seems mandatory but also 
very expensive unless we can garbage collect them at some point. 

> 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, 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to