On 7/22/2016 4:02 AM, Alessandro Bon wrote: > Issue: Full index replicas occur sometimes on master startup and after > commits, despite only the <str name="replicateAfter">optimize</str> > directive is specified. In the case of replica on commit, it occurs > only for sufficiently big commits. Replica correctly starts again at > the end of my indexing job, after the optimization phase. As result of > this behaviour I get incomplete indexes on slaves during the indexing > process.
There's a known bug where full index replication happens after master restart. This was supposed to be fixed in 5.5.2and 6.1.0, but you say you are running 5.5.2. https://issues.apache.org/jira/browse/SOLR-9036 All replications are *supposed* to be delta replications -- only new/changed files. Note that normal commits can cause segment merging, up to and including the entire index if conditions are just right. Segment merges can result in new segment files that are very large, which could take a long time to replicate. Optimizing the index is a forced merge to one segment. This will always lead to a full-index replication, because the entire index is rewritten into a single segment and all the other segment files are deleted. You might want to give SolrCloud a try. There are no masters and no slaves. It is a true redundant cluster. Thanks, Shawn
