Thanks, just wanted to make one other comment. In my case, there were no
"segments_..." files created prior to the crash, so I don't think we can
safely rely on their presence/content.
On Thu, May 30, 2013 at 8:21 AM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> I opened https://issu
I opened https://issues.apache.org/jira/browse/LUCENE-5024 to see if
we can improve this ...
Mike McCandless
http://blog.mikemccandless.com
On Thu, May 30, 2013 at 7:31 AM, Michael McCandless
wrote:
> Hi Vitaly,
>
> This is unfortunately due to a recent change in IndexWriter ... search
> for
Hi Vitaly,
This is unfortunately due to a recent change in IndexWriter ... search
for the recent thread "CorruptIndexException when opening Index during
first commit" on this list.
Normally, if a commit fails for any reason (OS, hardware, JVM crashes)
we simply fall back to the last commit and no
I have encountered a strange issue, that appears to be pretty hard to hit,
but is still a serious problem when it does occur. It seems that if the JVM
crashes in a racy fashion with instantiation of IndexWriter, the index may
be left in an inconsistent state. An attempt to reload such an index on
r
