Technologies/Trino/trino.execution.queued_queries
TrinoTrinoMetric

trino.execution.queued_queries

Queries waiting in queue
Dimensions:None
Available on:Native (1)PrometheusPrometheus (1)DatadogDatadog (1)
Interface Metrics (3)
Native
Number of queries currently waiting in the queue
Dimensions:None
PrometheusPrometheus
Number of queries waiting in the queue
Dimensions:None
DatadogDatadog
Number of queries currently queued awaiting execution
Dimensions:None
Sources
trino.execution.QueryManager.QueuedQueriestrino.io
trino.execution.queued_queriesdocs.datadoghq.com

Technical Annotations (20)

Configuration Parameters (7)
retry-policyrecommended: QUERY
Use QUERY for small queries to avoid task-level retry overhead
query.remote-task.max-error-durationrecommended: 1m
Maximum time to wait before abandoning a remote task, may cause premature failures
query-retry-attemptsrecommended: 2
Number of retry attempts, could contribute to retry loops if failures are consistent
query.max-concurrent-queriesrecommended: lower limit under high concurrency
controls query admission to prevent thread pool exhaustion
task.max-drivers-per-taskrecommended: lower for resource-heavy queries
reduces per-query resource consumption
query.client.timeoutrecommended: 5m
Maximum time to wait for query execution to begin
query.execution-policyrecommended: phased
default policy that maximizes utilization and minimizes wall time
Error Signatures (1)
Waited 5.00m for at least 1 workerslog pattern
CLI Commands (2)
EXPLAIN ANALYZE <query>diagnostic
SELECT max(running_queries) AS max_concurrency FROM (SELECT count(*) AS running_queries, create_time FROM trino_events.trino_queries WHERE create_time >= now() - interval '1' day AND state = 'RUNNING' GROUP BY create_time) t;diagnostic
Technical References (10)
Metabase v0.51.12componentStarburst Metabase driver v5.0componentTrino v457componenttrino_events.trino_queriescomponentresource groupconceptresource groupsconceptadmission controlconceptnode-state-pollercomponentresource group managementconceptcoordinatorcomponent
Related Insights (13)
TASK retry policy increases latency for short-running querieswarning
▸
Insufficient capacity causes excessive query queuingwarning
▸
Cluster intermittently enters idle state after initial query executioncritical
▸
Query phase timing reveals specific performance bottleneck typesinfo
▸
High query concurrency causes resource contentionwarning
▸
High query concurrency exhausts worker thread pool resourceswarning
▸
Query execution blocked waiting 5 minutes for worker node availabilitycritical
▸
All-at-once execution policy increases queue time and wall timeinfo
▸
All-at-once execution policy increases queue times and query wall timeinfo
▸
Query queuing and inconsistent response times from concurrent session contentionwarning
▸
Coordinator bottleneck from hundreds of concurrent analystswarning
▸
High query concurrency indicates capacity constraintswarning
▸
All-at-once execution policy causes increased queue timeswarning
▸