trino.execution.canceled_queries.one_minute

Canceled queries last minute

Dimensions:None

Available on:

Datadog (1)

Interface Metrics (1)

Datadog

trino.execution.canceled_queries.one_minute.count

Count of canceled queries in the last minute

Dimensions:None

Sources

trino.execution.canceled_queries.one_minute.countdocs.datadoghq.com

Technical Annotations (10)

Configuration Parameters (5)

query.client.timeoutrecommended: 5m

Default timeout before abandoning queries without client contact

query.max-planning-timerecommended: 10m

Default max planning time before cancellation attempt

query.max-scan-physical-bytes

No default set; configure to prevent excessive scans

query.max-write-physical-size

No default set; configure to prevent excessive writes

query.max-execution-time

Max query execution time in config.properties; increase if legitimate queries are timing out

Error Signatures (1)

QUERY_CANCELEDerror code

CLI Commands (2)

SELECT state, COUNT(*) AS count FROM trino_events.trino_queries WHERE create_time >= now() - interval '7' day GROUP BY state;

diagnostic

SELECT error_code, error_name, COUNT(*) AS failures FROM trino_events.trino_queries WHERE state = 'FAILED' AND create_time >= now() - interval '30' day GROUP BY error_code, error_name ORDER BY failures DESC LIMIT 10;

diagnostic

Technical References (2)

trino_events.trino_queriescomponentstatecomponent

Related Insights (7)

Query failures and cancellations indicate platform or workload issueswarning

▸

Client disconnection causes query abandonment after timeoutwarning

▸

High query failure rate indicates operational issueswarning

▸

Query planning timeout with non-cancellable operationswarning

▸

Runaway queries terminated at scan or write limitswarning

▸

Queries canceled due to memory or CPU limit exceededwarning

▸

Queries canceled when execution time exceeds configured limitwarning

▸