[
https://issues.apache.org/jira/browse/SOLR-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker updated SOLR-6606:
--------------------------------
Attachment: SOLR-6606.patch
Patch where the auto (hard) commit command is executed only on the leader and
subsequently forwarded to it's replicas.
The current tests pass but I am unsure how many of them actually triggered this
code path.
I wanted to get some feedback as to what everyone feels about this approach
before writing additional tests
> 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: [email protected]
For additional commands, e-mail: [email protected]
