Elasticsearch Search Rejected Queue

Average Read Time

2 Mins

Elasticsearch Search Rejected Queue

Opster Team

May 23, 2022

Average Read Time

2 Mins

In addition to reading this guide, we recommend you run the Elasticsearch Health Check-Up. It will detect issues and improve your Elasticsearch performance by analyzing your shard sizes, threadpools, memory, snapshots, disk watermarks and more.

The Elasticsearch Check-Up is free and requires no installation.

If you’re suffering from search related issues or poor search performance, you should run Opster’s free Search Log Analyzer to optimize your searches.

With Opster’s Analyzer, you can easily locate slow searches and understand what led to them adding additional load to your system. You’ll receive customized recommendations for how to handle rejected searches and improve your search performance. The tool is free and takes just 2 minutes to run.

What it means

If the Elasticsearch cluster starts to reject search requests, there could be a number of causes. Generally it indicates that one or more nodes cannot keep up with the volume of search requests, resulting in a queue building up on that node. Once the queue exceeds the search queue maximum size, then the node will start to reject the requests.

How to resolve it

Check to see the state of the thread pool, to find out whether the search rejections are always occurring on the same node, or are spread across all of the nodes.

GET /_cat/thread_pool/search
  • It may be useful to activate slow search query logging as described in this guide.

To minimize the impact of distressed node on your search queries, make sure you have the following setting on your cluster (version 6.1 and above):

PUT /_cluster/settings
  "transient": {
    "cluster.routing.use_adaptive_replica_selection": true

Run the Check-Up to get a customized report like this:

Analyze your cluster
Skip to content