[
https://issues.apache.org/jira/browse/SOLR-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246712#comment-14246712
]
Varun Thacker commented on SOLR-6606:
-------------------------------------
This is how I started testing on my local machine:
1. created a collection with one shard and two replicas
2. Keep indexing new documents. Batch size=1000. autoCommit every 10k docs.
3. Now every few minutes, I ran this command -
./solr stop -p 7574; sleep 100;./solr start -cloud -d node2 -p 7574 -z
localhost:9983
4. Stopped indexing.
When we kill a server and bring it back up, replication handler will pull all
the missing segment files which are missing, so both replicas will have same
segment files after recovery. Now both replicas keep creating segment files in
a similar fashion even without the leader distributing auto-commmit.
>From what I understand since replication checks if the file name and size is
>the same ( and not segment ids or anything like that ) we get away with it.
I think since moving replication to use segment ids is something we are
considering given SOLR-6640 , I am tempted to explore that first and revisit
this.
Any thought? Am I missing something during the tests or interpreting
incorrectly?
> 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]
