Could this have something to do with the hardlinks of the snapshots? I mean... the snapcleaner removes the snapshots but... maybe somthing remains in there until tomcat is restarted?
Marc Sturlese wrote: > > Hey there, > Something really weird happened with my indexer... I have an index of 2G > more or less and I am running cron jobs to keep it updated every 15 min > (the size of the index keeps always the same more or less as I just update > docs). Every time the update is done I optimize the index and send it to > the slaves using the scripts of collection distribution. > I optimize it every time because if not, searchtime becomes much more > slow... > The problem comes here... after 2 days of upates... tomcat broke saying > there was no mor space left on device. Doing a df -m ... the partition > where I have the index was at 100% but doing a du -m of the folder > index... it was using half of the available space. > So... I restart tomcat and everything was alrite again.. I mean ... a df > -m was showing that just half of the partition was used. > I have to say I just keep 2 snapshots of the index. Always delete the > others with cronjob using snapcleaner. > I have thought maybe it has something to do with the snapcleaner... maybe > after delete the snapshoots tomcat still thinks that the space is in > use...? > I really would apreciate any advice with this because I am really lost > with this problem... > If I didn't explain myself well or details are missing let me know > please... > > > -- View this message in context: http://www.nabble.com/Really-weird-behabiour-with-the-indexer-with-cronjobs-tp22409623p22412642.html Sent from the Solr - User mailing list archive at Nabble.com.
