ElasticsearchMetricelasticsearch.node.thread_pool.tasks.queued
Queued thread pool tasksDimensions:None
Summary
Measures the number of tasks waiting in thread pool queues for execution. Elasticsearch uses multiple thread pools (search, write, bulk, etc.) with bounded queues. Growing queues indicate resource saturation, and queue rejections (when full) cause 429 errors. The insight about thread pool rejections highlights this as a critical indicator of cluster overload requiring scaling or query optimization.
Interface Metrics (10)
Datadog
Dimensions:None
DatadogDimensions:None
DatadogDimensions:None
OpenTelemetryDimensions:None
DatadogDimensions:None
DatadogDimensions:None
DatadogDimensions:None
DatadogDimensions:None
Sources
elasticsearch.thread_pool.fetch_shard_started.activegithub.com
elasticsearch.thread_pool.fetch_shard_started.rejectedgithub.com
elasticsearch_thread_pool_queue_countwww.dynatrace.com
thread_pool_queue_countgithub.com
elasticsearch.thread_pool.fetch_shard_started.queuegithub.com
elasticsearch.node.thread_pool.tasks.queuedgithub.com
elasticsearch.thread_pool.force_merge.activegithub.com
elasticsearch.thread_pool.force_merge.queuegithub.com
elasticsearch.thread_pool.fetch_shard_store.activegithub.com
elasticsearch.thread_pool.fetch_shard_store.queuegithub.com
Related Insights (2)
Thread Pool Rejections Indicate Overloadcritical
Thread pool queue saturation causes Elasticsearch to reject incoming requests, indicating the cluster cannot process the current load. Search, write, and bulk thread pools are most commonly affected.
▸
Task Management Queue Buildupwarning
Long-running or stuck tasks accumulate in the task manager, potentially blocking critical operations and consuming resources.
▸