Runbook

High Number of Queued Threads in Elasticsearch Thread Pool

Back to Runbooks

Overview

This incident type occurs when the number of queued threads in a thread pool in elasticsearch is higher than the acceptable limit. This may indicate that the thread pool is unable to handle the current workload, which can lead to performance issues and delays in processing requests. It is important to investigate and address this issue promptly to ensure optimal performance of the system.

Parameters

Debug

Check the number of queued threads in Elasticsearch

Check the number of available threads in Elasticsearch

Check the number of active threads in Elasticsearch

Check the number of rejected requests in Elasticsearch

Check the number of completed requests in Elasticsearch

Check the number of failed requests in Elasticsearch

Repair

Increase the number of threads available in the thread pool in elasticsearch to avoid excessive queuing.

Learn more

Related Runbooks

Check out these related runbooks to help you debug and resolve similar issues.