lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrzej Bialecki ...@getopt.org>
Subject Re: Help to determine why an optimized index is proportionaly too big.
Date Fri, 10 Apr 2009 15:53:53 GMT
Chris Hostetter wrote:
> : The second stage index failed an optimization with a disk full exception 
> : (I had to move it to another lucene machine with a larger disk partition 
> : to complete the optimization. Is there a reason why a 22 day index would 
> : be 10x the size of an 8 day index when the document indexing rate is 
> : fairly constant? Also, is there a way to shrink the index without 
> : regenerating it?
> 
> did you run CheckIndex after it failed to optimize the first time?  the 
> failure may have left old temp files arround that aren't actually part of 
> the index but are taking up space. 
> 
> (Actually: does CheckIndex warn about unused files in the index directory 
> so people can clean them up? i'm not sure)

It doesn't. But Luke has a function to do this.


-- 
Best regards,
Andrzej Bialecki     <><
  ___. ___ ___ ___ _ _   __________________________________
[__ || __|__/|__||\/|  Information Retrieval, Semantic Web
___|||__||  \|  ||  |  Embedded Unix, System Integration
http://www.sigram.com  Contact: info at sigram dot com


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Mime
View raw message