Hi Jasper, Solr does handle that for you. Some more stuff to share:
* Solr version? * JVM version? * OS? * Java replication? * Errors in Solr logs? * deletion policy section in solrconfig.xml? * merge policy section in solrconfig.xml? * ... You may also want to look at your Index report in SPM (http://sematext.com/spm) before/during/after replication and share what you see. Otis ---- Performance Monitoring for Solr / ElasticSearch / HBase - http://sematext.com/spm ----- Original Message ----- > From: Jasper Floor <jasper.fl...@m4n.nl> > To: solr-user@lucene.apache.org > Cc: > Sent: Thursday, May 10, 2012 9:08 AM > Subject: slave index not cleaned > > Perhaps I am missing the obvious but our slaves tend to run out of > disk space. The index sizes grow to multiple times the size of the > master. So I just toss all the data and trigger a replication. > However, can't solr handle this for me? > > I'm sorry if I've missed a simple setting which does this for me, but > if its there then I have missed it. > > mvg > Jasper >
