trino-admin-cluster-health

Diagnose Trino cluster health via REST endpoints, JMX metrics, and logs.

14|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/ivanshamaev/de-agent-skills --skill trino-admin-cluster-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trino-admin-cluster-health
Source: https://github.com/ivanshamaev/de-agent-skills/tree/main/group_skills/trino_group_skills/trino_admin_cluster_health
Command: npx skills add https://github.com/ivanshamaev/de-agent-skills --skill trino-admin-cluster-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly diagnose why a Trino cluster is slow, unhealthy, or failing by surfacing coordinator and worker status, query states, memory pressure, and operational signals from REST, JMX/metrics, logs, and the Web UI.

Core Features & Use Cases

  • Cluster health checks via REST: Validate coordinator readiness, enumerate nodes, inspect cluster-wide running/queued/blocked query counts, and view or terminate problematic queries.
  • Memory and stability visibility via JMX metrics: Export key runtime and OOM-related counters to Prometheus and use alerting to catch worker instability and resource pressure early.
  • Operational diagnosis from query state and logs: Identify BLOCKED/QUEUED conditions, correlate them with OOM kills and worker loss patterns, and perform safe rolling shutdowns.

Use case: you observe unexpected queuing and intermittent failures during peak load, so you check cluster endpoints, confirm blocked/running/query queue depth, verify OOM kills or free-memory drops, then determine whether a graceful worker shutdown or configuration change (resource/memory limits, spill behavior) is needed.

Quick Start

Use the trino-admin-cluster-health skill to diagnose a slow Trino cluster by checking /v1/info, /v1/cluster, /v1/node, and inspecting blocked or long-running queries, metrics, and relevant server logs.

Frequently Asked Questions about trino-admin-cluster-health

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose why my Trino cluster is slow or queries are queuing?

Diagnose slow Trino clusters by checking /v1/info, /v1/cluster, and /v1/node REST endpoints to inspect running and blocked query counts, then correlate those with worker status and server logs to identify the root cause.

What causes memory pressure and OOM kills in Trino workers?

Memory pressure in Trino workers is identified by correlating BLOCKED or QUEUED query states with JMX MBean metrics for OOM-related counters and free-memory drops in logs, guiding configuration changes or graceful shutdowns.

How do I monitor Trino cluster health with Prometheus and Grafana alerts?

Monitor Trino cluster health by exporting key runtime and OOM-related counters via JMX MBean metrics to Prometheus, then setting up Grafana alerts to catch worker instability and resource pressure early.

What is the best way to perform a safe rolling restart of Trino workers?

Perform safe rolling restarts by checking /v1/node to enumerate active nodes and inspecting query states via /v1/query, ensuring throughput drops are minimized before initiating graceful worker shutdowns.

Can I terminate problematic long-running queries directly via Trino REST endpoints?

Yes, you can view or terminate problematic queries by accessing the /v1/query REST endpoint to inspect BLOCKED or long-running states and manage them directly to resolve cluster throughput issues.

When should I adjust Trino memory limits or spill behavior during incident triage?

Adjust Trino memory limits or spill behavior when operational diagnosis confirms OOM kills, worker loss patterns, or free-memory drops correlated with BLOCKED and QUEUED query conditions during peak load.