, October 29, 2011 10:55 AM
To: java-user@lucene.apache.org
Subject: Re: data corruption in lucene index 2.3.2
That's fine -- the reader is read-only and won't corrupt the index if
the machine/OS crashes while it's open.
Oh, actually: Lucene 2.3.x did not properly fsync files when
> To: java-user@lucene.apache.org
> Subject: Re: data corruption in lucene index 2.3.2
>
>
> Was there any catastrophic event against this index?
>
> EG, power loss on the machine, or OS crash, while the app had and
> IndexWriter open?
>
> Mike McCandless
>
> http://
...@mikemccandless.com]
Sent: Saturday, October 29, 2011 3:39 AM
To: java-user@lucene.apache.org
Subject: Re: data corruption in lucene index 2.3.2
Was there any catastrophic event against this index?
EG, power loss on the machine, or OS crash, while the app had and
IndexWriter open?
Mike McCandless
Was there any catastrophic event against this index?
EG, power loss on the machine, or OS crash, while the app had and
IndexWriter open?
Mike McCandless
http://blog.mikemccandless.com
On Fri, Oct 28, 2011 at 4:57 PM, Zhang, Lisheng
wrote:
>
> We are using lucene 2.3.2 (yes we should upgrade) a
