Hm, I don't know what to do anymore. I tried this: - Run Tomcat service as local administrator to overcome any permissioning issues - Installed latest nightly build (I noticed that item I mentioned before ( http://markmail.org/message/yq2ram4f3jblermd) had been committed which is good - Build a small master and slave core to try it all out - With each replication, the number of files on slave grows, and the directories index.xxxxxxx.. are not removed - I tried sending explicit commit commands to the slave, assuming it wouldn't help, which was true. - I don't see any reference to SolrDeletion in the log of the slave (it's there in the log of the master)
Can anybody recommend some action to be taken? I'm building up some quite large production cores right now, and don't want the slaves to eat up all hard disk space of course.. Thanks a lot in advance, Jaoc. 2009/1/21 Noble Paul നോബിള് नोब्ळ् <noble.p...@gmail.com> > On Wed, Jan 21, 2009 at 3:42 PM, Jaco <jdevr...@gmail.com> wrote: > > Thanks for the fast replies! > > > > It appears that I made a (probably classical) error... I didnt' make the > > change to solrconfig.xml to include the <deletionPolicy> when applying > the > > upgrade. I include this now, but the slave is not cleaning up. Will this > be > > done at some point automatically? Can I trigger this? > Unfortunately , no. > Lucene is supposed to cleanup these old commit points automatically > after each commit. Even if the <delettionPolicy> is not specified the > default is supposed to take effect. > > > > User access rights for the user are OK, this use is allowed to do > anything > > in the Solr data directory (Tomcat service is running from SYSTEM account > > (Windows)). > > > > Thanks, regards, > > > > Jaco. > > > > > > 2009/1/21 Shalin Shekhar Mangar <shalinman...@gmail.com> > > > >> Hi, > >> > >> There shouldn't be so many files on the slave. Since the empty > index.xxxxx > >> folders are not getting deleted, is it possible that Solr process user > does > >> not enough privileges to delete files/folders? > >> > >> Also, have you made any changes to the IndexDeletionPolicy > configuration? > >> > >> On Wed, Jan 21, 2009 at 2:15 PM, Jaco <jdevr...@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. > >> > > >> > >> > >> > >> -- > >> Regards, > >> Shalin Shekhar Mangar. > >> > > > > > > -- > --Noble Paul >
