lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McCandless <luc...@mikemccandless.com>
Subject Re: Help to determine why an optimized index is proportionaly too big.
Date Thu, 09 Apr 2009 23:33:01 GMT
On Thu, Apr 9, 2009 at 6:46 PM, Chris Hostetter
<hossman_lucene@fucit.org> 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)

Actually, it doesn't (it only checks the "live" index files).

But: IndexWriter will remove unreferenced files as soon as it's instantiated.

Mike

---------------------------------------------------------------------
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