This turned out to be a missing SolrDeletionPolicy in the configuration. Once the slaves had a SolrDeletionPolicy, they stopped growing out of control.
Ian. On Wed, Aug 17, 2011 at 8:46 AM, Ian Connor <ian.con...@gmail.com> wrote: > Hi, > > We have noticed that many index.* directories are appearing on slaves (some > more than others). > > e.g. ls shows > > index/ index.20110101021510/ index.20110105030400/ > index.20110106040701/ index.20110130031416/ > index.20101222081713/ index.20110101034500/ index.20110105075100/ > index.20110107085605/ index.20110812153349/ > index.20101231011754/ index.20110105022600/ index.20110106024902/ > index.20110108014100/ index.20110814204200/ > > Are this harmful, should I clean them out. I see a command for backup > cleanup but am not sure the best way to clean these up (apart from removing > all index* and getting a fresh replica). > > We have also seen on the latest 3.4 build that replicas are getting 1000s > of files even though the masters have less than a 100 each. It seems as > though they are not deleting after some replications and not sure if this is > also related. We are trying to monitor this to see if we can find out how to > reproduce it or at least the conditions that tend to reproduce it. > > -- > Regards, > > Ian Connor > 1 Leighton St #723 > Cambridge, MA 02141 > Call Center Phone: +1 (714) 239 3875 (24 hrs) > Fax: +1(770) 818 5697 > Skype: ian.connor >
