Hi,
I think that you may be using a Lucene/Solr IndexDeletionPolicy that does
not remove old commits (and you aren't propagating solr-config via
replication).
You can configre this feature on the solr-config.xml inside the
<deletionPolicy> tag:
*<deletionPolicy class="solr.SolrDeletionPolicy">
<!-- The number of commit points to be kept -->
<str name="maxCommitsToKeep">1</str>
<!-- The number of optimized commit points to be kept -->
<str name="maxOptimizedCommitsToKeep">0</str>
<!--
Delete all commit points once they have reached the given age.
Supports DateMathParser syntax e.g.
<str name="maxCommitAge">30MINUTES</str>
<str name="maxCommitAge">1DAY</str>
-->
</deletionPolicy>*
I hope this can be helpful.
Cheers,
Tommaso
2010/7/26 Muneeb Ali <muneeba...@hotmail.com>
>
> Hi,
>
> I am using Solr 1.4 version, with master-slave setup. We have one master
> slave and two slave servers. It was all working fine, but lately solr
> slaves
> are behaving strange. Particularly during replicating the index, the slave
> nodes die and always need a restart. Also the index size of slave nodes is
> much bigger (336GB) than the master node index (i.e. only 86GB).
>
> I am guessing that its not removing previous indices at slave nodes when
> replicating? Has anyone faced similar issues?
>
> Any help would be highly appreciated.
>
> Thanks very much.
>
> -Muneeb
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/slave-index-is-bigger-than-master-index-tp996329p996329.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
