NullPointerException in ConcurrentMergeScheduler

[rdeaton]

org.apache.lucene.index.MergePolicy$MergeException: java.lang.NullPointerException
at org.elasticsearch.index.merge.scheduler.ConcurrentMergeSchedulerProvider$CustomConcurrentMergeScheduler.handleMergeException(ConcurrentMergeSchedulerProvider.java:99)
at org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:518)
Caused by: java.lang.NullPointerException
at org.elasticsearch.search.suggest.completion.AnalyzingCompletionLookupProvider$1$1.finish(AnalyzingCompletionLookupProvider.java:134)
at org.elasticsearch.search.suggest.completion.Completion090PostingsFormat$SuggestFieldsConsumer$1.finish(Completion090PostingsFormat.java:152)
at org.apache.lucene.codecs.TermsConsumer.merge(TermsConsumer.java:204)
at org.apache.lucene.codecs.FieldsConsumer.merge(FieldsConsumer.java:72)
at org.apache.lucene.index.SegmentMerger.mergeTerms(SegmentMerger.java:365)
at org.apache.lucene.index.SegmentMerger.merge(SegmentMerger.java:98)
at org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3772)
at org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:3376)
at org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeScheduler.java:405)
at org.apache.lucene.index.TrackingConcurrentMergeScheduler.doMerge(TrackingConcurrentMergeScheduler.java:91)
at org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:482)

As always, let me know if there's anything more I can provide to help debug.

[s1monw]

this is already fixed ie. duplicate of #3555

[rdeaton]

This was on master from this morning, so perhaps it's not quite fixed yet?

[s1monw]

Well, that line number points to a comment in the code and they tend to be correct though. I am wondering if what you have deployed is actually the current HEAD of our master branch or an older revision. Can you check what has you build that from?

[rdeaton]

Oops, seems you're right, I was correlating logs to the wrong cluster. Sorry for the mixup.

[s1monw]

@rdeaton thanks for clarifying!