You are viewing a plain text version of this content. The canonical link for it is here.

Posted to solr-user@lucene.apache.org by Noble Paul നോബിള്‍ नोब्ळ् <no...@gmail.com> on 2009/01/21 10:03:53 UTC

Re: Solr Replication: disk space consumed on slave much higher than on master

the index.xxx directories are supposed to be deleted (automatically).
you can safely delete them.

But, I am wondering why the index files in the slave did not get
deleted. By default the deletionPolicy is KeepOnlyLastCommit.



On Wed, Jan 21, 2009 at 2:15 PM, Jaco <jd...@gmail.com> wrote:
> Hi,
>
> I'm running Solr nightly build of 20.12.2008, with patch as discussed on
> http://markmail.org/message/yq2ram4f3jblermd, using Solr replication.
>
> On various systems running, I see that the disk space consumed on the slave
> is much higher than on the master. One example:
> - Master: 30 GB in 138 files
> - Slave: 152 GB in 3,941 files
>
> Can anybody tell me what to do to prevent this from happening, and how to
> clean up the slave? Also, there are quite some empty index.xxxxxxx
> directories sitting in the slaves data dir. Can these be safely removed?
>
> Thanks a lot in advance, bye,
>
> Jaco.
>



-- 
--Noble Paul