Positions increment gap must be positive got – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.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 the “positions_increment_gap” parameter in Elasticsearch is set to a negative value. This parameter is used to control the number of fake term position which should be inserted between each instance of a field. It must be a positive number. To resolve this issue, you should check your Elasticsearch settings or mapping configurations and ensure that the “positions_increment_gap” parameter is set to a positive value. If it’s not, change it to a positive number and restart Elasticsearch.

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 ” [positions_increment_gap] must be positive; got ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugins, index.

Log Context

Log “[positions_increment_gap] must be positive; got” class name is AnnotatedTextFieldMapper.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 builder = this;
 }  public Builder positionIncrementGap(int positionIncrementGap) {
 if (positionIncrementGap < 0) {
 throw new MapperParsingException("[positions_increment_gap] must be positive; got " + positionIncrementGap);
 this.positionIncrementGap = positionIncrementGap;
 return this;


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?

Get expert answers on Elasticsearch/OpenSearch