What version of Solr and what operating system? But regardless, this shouldn't be happening. Indexes can temporarily double in size, but any extras should be cleaned up relatively soon.
On the master, what's the total size of the <solr home>/data directory? I'm a little suspicious of the <backupAfter> on your master, but I don't think that's the root of your problem.... Are you recreating the index on the master (by deleting the index directory and starting over)? This is unusual, and I suspect it's something odd in your configuration, but I confess I'm at a loss as to what. Best Erick On Fri, Mar 23, 2012 at 10:28 AM, Alexandre Rocco <alel...@gmail.com> wrote: > Hello, > > We have a Solr index that has an average of 1.19 GB in size. > After configuring the replication, the slave machine is growing the index > size expoentially. > Currently we have an slave with 323.44 GB in size. > Is there anything that could cause this behavior? > The current replication config is below. > > Master: > <requestHandler name="/replication" class="solr.ReplicationHandler"> > <lst name="master"> > <str name="replicateAfter">commit</str> > <str name="replicateAfter">startup</str> > <str name="backupAfter">startup</str> > <str name="confFiles"> > elevate.xml,protwords.txt,schema.xml,spellings.txt,stopwords.txt,synonyms.txt > </str> > </lst> > </requestHandler> > > Slave: > <requestHandler name="/replication" class="solr.ReplicationHandler"> > <lst name="slave"> > <str name="masterUrl">http://master:8984/solr/Index/replication</str> > </lst> > </requestHandler> > > Any pointers will be useful. > > Thanks, > Alexandre
