Thanks for the response, Mike.
If I understand correctly, the problem was incorrectly identifying a large
corrupted index as a non-existant index? It seems like you'd really want
an index with first-commit in progress to behave like an index with zero
documents, as opposed to a non-existant inde
Unfortunately this is expected behavior.
We tried to fix it in LUCENE-2812, but this fix was too dangerous and
could sometimes erase a good index (if transient IOExcs are happening,
e.g. due to file descriptor exhaustion) so we reverted back in
LUCENE-4738, so that indexExists will return true, an
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 co
Hi Simon,
Thanks for the quick response! I just created
https://issues.apache.org/jira/browse/LUCENE-5002.
Sergiusz
On Wed, May 15, 2013 at 11:49 PM, Simon Willnauer
wrote:
> This seems like a bug caused due to the fact that we moved the CFS
> building into DWPT. Can you open an issue for this?
