lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Wistow <>
Subject Re: flush, optimize and FileNotFound exceptions
Date Tue, 03 Apr 2007 12:40:34 GMT
On Tue, Apr 03, 2007 at 08:31:20AM -0400, Michael McCandless said:
> Optimize actually does its own flush before optimizing, so you don't
> need to call it yourself and in fact calling it after optimize will
> just be a harmless no-op.

Ah, that's good to know.
> You should be worried about this exception.  It means there's some
> sort of index corruption going on.  What version of Lucene are you on?
> If you haven't upgraded to 2.1 you should try to do so; 2.1 has fixed
> a number of cases that can lead to errant IOExceptions.

Oops, no, still running on 2.0

> I would double and triple check that indeed you indeed only have one
> writer against the index; accidentally having 2 writers on the same
> index (which is normally prevented by the write lock) could cause
> exactly this exception.

Thanks for the advice - I'll try the upgrade and then try and get it 
down to a test case. 


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message