I will but I bet I can guess what happened -- this index has many duplicates in it as well (same uniqueKey id multiple times) - this happened to us once before and it was because the solr server went down during an add. We may have to re-index, but I will run checkIndex now. Thanks (Thread for dupes here : http://mail-archives.apache.org/mod_mbox/lucene-solr-user/200803.mbox/%3c4ed8c459-1b0f-41cc-986c-4ffceef82...@variogr.am%3e)
On Fri, Jan 2, 2009 at 3:44 PM, Michael McCandless < luc...@mikemccandless.com> wrote: > It looks like your index has some kind of corruption. Were there any other > exceptions prior to this one, or, any previous problems with the OS/IO > system? > > Can you run CheckIndex (java org.apache.lucene.index.CheckIndex to see > usage) and post the output? > Mike > > Brian Whitman <br...@echonest.com> wrote: > > > I am getting this on a 10GB index (via solr 1.3) during an optimize: > > Jan 2, 2009 6:51:52 PM org.apache.solr.common.SolrException log > > SEVERE: java.io.IOException: background merge hit exception: > _ks4:C2504982 > > _oaw:C514635 _tll:C827949 _tdx:C18372 _te8:C19929 _tej:C22201 > > _1agw:C1717926 > > _1agz:C1 into _1ah2 [optimize] > > at org.apache.lucene.index.IndexWriter.optimize(IndexWriter.java:2346) > > at org.apache.lucene.index.IndexWriter.optimize(IndexWriter.java:2280) > > at > > > > > org.apache.solr.update.DirectUpdateHandler2.commit(DirectUpdateHandler2.java:355) > > at > > > > > org.apache.solr.update.processor.RunUpdateProcessor.processCommit(RunUpdateProcessorFactory.java:77) > > ... > > > > Exception in thread "Lucene Merge Thread #2" > > org.apache.lucene.index.MergePolicy$MergeException: > > java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 34950 > > at > > > > > org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(ConcurrentMergeScheduler.java:314) > > at > > > > > org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:291) > > Caused by: java.lang.ArrayIndexOutOfBoundsException: Array index out of > > range: 34950 > > at org.apache.lucene.util.BitVector.get(BitVector.java:91) > > at org.apache.lucene.index.SegmentTermDocs.next(SegmentTermDocs.java:125) > > at > > > > > org.apache.lucene.index.SegmentTermPositions.next(SegmentTermPositions.java:98) > > ... > > > > > > Does anyone know how this is caused and how I can fix it? It happens with > > every optimize. Commits were very slow on this index as well (40x as slow > > as > > a similar index on another machine) I have plenty of disk space (many > 100s > > of GB) free. > > >
