Exception in the logs from IndexUpgrader (ArrayIndexOutOfBoundsException from FixedBitSet.set)

[Trejkaz <tr...@trypticon.org>]

Hi all.

Someone saw IndexUpgrader from 4.10.4 throw this when upgrading their index:

    Caused by: java.lang.ArrayIndexOutOfBoundsException: 191
        at org.apache.lucene.util.FixedBitSet.set(FixedBitSet.java:252)
        at org.apache.lucene.codecs.PostingsConsumer.merge(PostingsConsumer.java:113)
        at org.apache.lucene.codecs.TermsConsumer.merge(TermsConsumer.java:164)
        at org.apache.lucene.codecs.FieldsConsumer.merge(FieldsConsumer.java:72)
        at org.apache.lucene.index.SegmentMerger.mergeTerms(SegmentMerger.java:399)
        at org.apache.lucene.index.SegmentMerger.merge(SegmentMerger.java:112)
        at org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:4196)
        at org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:3784)
        at org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeScheduler.java:409)
        at org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:486)

Two questions:

  (1) Does this just mean the index is corrupt?

  (2) Shouldn't an exception merging cause IndexUpgrader to fail? We
only noticed this issue because of an exception from the Lucene _5_
IndexUpgrader on the resulting index, and it found V3 segments in the
index still, but we run the V4 upgrader first.

TX

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org