Yikes... not good. This shouldn't be due to anything you did wrong Ian... it looks like a lucene bug.
Some questions: - what platform are you running on, and what JVM? - are you using multicore? (I fixed some index locking bugs recently) - are there any exceptions in the log before this? - how reproducible is this? -Yonik On Thu, Aug 14, 2008 at 2:47 PM, Ian Connor <[EMAIL PROTECTED]> wrote: > Hi, > > I have rebuilt my index a few times (it should get up to about 4 > Million but around 1 Million it starts to fall apart). > > Exception in thread "Lucene Merge Thread #0" > org.apache.lucene.index.MergePolicy$MergeException: > java.lang.IndexOutOfBoundsException: Index: 105, Size: 33 > at > org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(ConcurrentMergeScheduler.java:323) > at > org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:300) > Caused by: java.lang.IndexOutOfBoundsException: Index: 105, Size: 33 > at java.util.ArrayList.rangeCheck(ArrayList.java:572) > at java.util.ArrayList.get(ArrayList.java:350) > at org.apache.lucene.index.FieldInfos.fieldInfo(FieldInfos.java:260) > at org.apache.lucene.index.FieldsReader.doc(FieldsReader.java:188) > at > org.apache.lucene.index.SegmentReader.document(SegmentReader.java:670) > at > org.apache.lucene.index.SegmentMerger.mergeFields(SegmentMerger.java:349) > at org.apache.lucene.index.SegmentMerger.merge(SegmentMerger.java:134) > at > org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3998) > at org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:3650) > at > org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeScheduler.java:214) > at > org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:269) > > > When this happens, the disk usage goes right up and the indexing > really starts to slow down. I am using a Solr build from about a week > ago - so my Lucene is at 2.4 according to the war files. > > Has anyone seen this error before? Is it possible to tell which Array > is too large? Would it be an Array I am sending in or another internal > one? > > Regards, > Ian Connor >
