According to https://issues.apache.org/jira/browse/LUCENE-1282?focusedCommentId=12596949#action_12596949 (Sun hotspot compiler bug in 1.6.0_04/05 affects Lucene), a workaround for the bug which causes the CorruptIndexException was put in to the 2.3 branch and 2.4. However, we are still experiencing this issue (intermittent creation of a corrupt index) with a 2.3-SNAPSHOT from maven. Was the workaround put into 2.3-SNAPSHOT? Are there other issues which would cause the same error (detailed below)?
We would prefer to avoid upgrading to JDK 6u10 (http://java.sun.com/javase/downloads/ea/6u10/6u10RC.jsp) until it is a final release, thus the use of the 2.3-SNAPSHOT dated July 22. Detailed error (seems to match LUCENE-1282): [java] org.apache.lucene.index.CorruptIndexException: doc counts differ for segment _1e: fieldsReader shows 2924328 but segmentInfo shows 2924329 [java] at org.apache.lucene.index.SegmentReader.initialize(SegmentReader.java:313) [java] at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:262) [java] at org.apache.lucene.index.SegmentReader.get(SegmentReader.java:230) [java] at org.apache.lucene.index.DirectoryIndexReader$1.doBody(DirectoryIndexReader.java:73) [java] at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:636) [java] at org.apache.lucene.index.DirectoryIndexReader.open(DirectoryIndexReader.java:63) [java] at org.apache.lucene.index.IndexReader.open(IndexReader.java:209) [java] at org.apache.lucene.index.IndexReader.open(IndexReader.java:173) Snapshot we are using: http://people.apache.org/maven-snapshot-repository/org/apache/lucene/lucene-core/2.3-SNAPSHOT/ (dated July 22) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
