Invalid gap policy: ” + text + “; accepted values: – Elasticsearch Error How To Solve Related Issues

Invalid gap policy: ” + text + “; accepted values: – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many errors 


This guide will help you check for common problems that cause the log “Invalid gap policy: ” + text + “; accepted values:” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: search, aggregations.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

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;


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Cross-thread operation not valid: Control accessed from a thread other than the thread it was created on -views 406,961 ,score 585

JsonMappingException: out of START_ARRAY token -views   306,042,score 101



About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now