Elasticsearch Index Queue Size Is High

By Opster Team

Updated: Jan 28, 2024

| 2 min read

Watch the video below for a quick overview of index and indexes in Elasticsearch:

Index and indexing in Elasticsearch - 3 min

Overview

If the Elasticsearch cluster starts to reject indexing requests, there could be a number of causes. Generally it is an indication that one or more nodes cannot keep up with the volume of indexing / delete / update / bulk requests, resulting in a queue building up on that node. Once the indexing queue exceeds the index queue maximum size (as defined here: Threadpools) then the node will start to reject the indexing requests.

How to resolve it

You should check the state of the thread pool to find out whether the indexing rejections are always occurring on the same node, or are spread across all of the nodes.

GET /_cat/thread_pool/index

Opster
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.