Hi Brian,
You might want to follow up on the Lucene list (java-u...@lucene.apache.org
). Something was causing problems with the merging and thus you ended
up with too many segments (hence the slow commits). I doubt that you
lost anything--usually the merge function doesn't modify the ind
I think I'm getting close with this (sorry for the self-replies)
I tried an optimize (which we never do) and it took 30m and said this a lot:
Exception in thread "Lucene Merge Thread #4"
org.apache.lucene.index.MergePolicy$MergeException:
java.lang.ArrayIndexOutOfBoundsException: Array index out
Not sure if these help. Here's the stack trace and jmap -histo output during
a long (bad) commit
Full thread dump Java HotSpot(TM) 64-Bit Server VM (11.0-b16 mixed mode):
"Attach Listener" daemon prio=10 tid=0x2aabf9954400 nid=0x5e1c runnable
[0x..0x42048d20]
java.la
