Hi, We're occasionally seeing a CorruptIndexException when a searcher is opened on a new index.
When we see the exception, it looks like what is happening is that the searcher is opening the index after prepareCommit for segments_1 but before the commit is completed. Because there is no prior commit to fall back to, lucene throws the CorruptIndexException. Does this sounds feasible and is it a bug? My expectation is that lucene would treat the index as nonexistent until the first commit is completed. We're running lucene 3.5. Cheers, Geoff
