[ https://issues.apache.org/jira/browse/SOLR-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227212#comment-14227212
]
Mark Miller commented on SOLR-6606:
-----------------------------------
I think you would really have to test out how well segments stay in sync - certainly they
can still go out of sync for various reasons, and you may have to use flush by document rather
than RAM to improve things (someone should do some real world testing), but otherwise, I think
you have an okay chance at some more segments lining up.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org