Invalid gap policy: ” + text + “; accepted values: – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Invalid gap policy: ” + text + “; accepted values: ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search and aggregations.

Log Context

Log “Invalid gap policy: [” + text + “]; accepted values:”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (result == null) {
 final List validNames = new ArrayList<>();
 for (GapPolicy policy : values()) {
 throw new ParsingException(tokenLocation; "Invalid gap policy: [" + text + "]; accepted values: " + validNames);
 return result;
 private final byte id;


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content