Failed to create index for percolator with nested document – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch fails to create an index for a percolator due to a nested document. This could be due to incorrect mapping or a complex nested structure. To resolve this, you can try simplifying the nested structure or ensure that the mapping is correctly defined. Also, check if the percolator query is correctly written and compatible with the nested document structure. Lastly, ensure that your Elasticsearch version supports nested documents in percolator queries.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” Failed to create index for percolator with nested document ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: percolator, index, document.

Log Context

Log “Failed to create index for percolator with nested document” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 assert directoryReader.leaves().size() == 1 : "Expected single leaf; but got [" + directoryReader.leaves().size() + "]";
 final IndexSearcher slowSearcher = new IndexSearcher(directoryReader);
 return slowSearcher;
 } catch (IOException e) {
 throw new ElasticsearchException("Failed to create index for percolator with nested document "; e);
 }  static PercolateQuery.QueryStore createStore(MappedFieldType queryBuilderFieldType; SearchExecutionContext context) {
 IndexVersion indexVersion = context.indexVersionCreated();


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?