You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Cao Manh Dat (JIRA)" <ji...@apache.org> on 2016/11/24 00:50:59 UTC
[jira] [Updated] (SOLR-6606) In cloud mode the leader should
distribute autoCommits to it's replicas
[ https://issues.apache.org/jira/browse/SOLR-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cao Manh Dat updated SOLR-6606:
-------------------------------
Attachment: SOLR-6606.patch
Updated patch for this issue. This patch updated to lastest source and fixed some bugs :
- set DistributedUpdateProcessor.COMMIT_END_POINT flag to distributed commit, so replica won't resend the commit back to leader
- increase retryCount in consistencyCheck()
- added a test ( which currently failed ) to make sure segments are line up in very simple case of adding one by one new documents
The test is failed because between the IW.commit() and open a new searcher in the replicas side. They can received some new documents so when they open a new searcher they may create a new segment ( which have different of documents for each replicas ) so segments between replicas is never be lined up.
The test is failed so often, hence I think in the real world we won't never get a single benefit from this patch.
> 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, 6.0
>
> Attachments: SOLR-6606.patch, 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