query

Diagnose slow or incorrect StarRocks queries from FE logs to BE execution profiles.

73|12|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/StarRocks/starrocks-debug-skills --skill query-starrocks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: query
Source: https://github.com/StarRocks/starrocks-debug-skills/tree/main/query
Command: npx skills add https://github.com/StarRocks/starrocks-debug-skills --skill query-starrocks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps diagnose StarRocks queries that are slow, hanging, returning wrong results, or consuming excessive memory by turning cluster symptoms into a structured investigation path.

Core Features & Use Cases

  • End-to-end query triage: Traces issues from FE receipt and live query state through BE execution, logs, and profiles.
  • Performance bottleneck analysis: Identifies scan skew, rowset merge overhead, predicate pushdown failures, join blowups, and missing statistics.
  • Bug localization workflow: Narrows down incorrect results or crashes by selectively disabling planner and execution features.
  • Use case: A production query times out after a deployment; this Skill helps determine whether the root cause is network saturation, FE lock contention, scan imbalance, or an oversized broadcast join.

Quick Start

Use the query skill to analyze a specific slow StarRocks query, inspect its audit log and profile, and guide me to the most likely root cause and next diagnostic step.

Frequently Asked Questions about query

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

FAQPage Schema
How do I diagnose a slow StarRocks query using profile analysis?

Identify StarRocks join bottlenecks by analyzing BE execution profiles for oversized broadcast joins. The process traces query execution from FE receipt to BE runtime, isolating whether the root cause is join blowup, scan skew, or network saturation.

Why does my StarRocks query hang and how can I troubleshoot it?

Troubleshoot a hanging StarRocks query by inspecting its current query state and FE logs. This investigation checks for FE lock contention or connection issues, tracing the execution path to determine where the query is stuck.

What causes scan skew in StarRocks and how do I fix it?

Identify scan skew in StarRocks by analyzing execution profiles for scan imbalance and rowset merge overhead. Fixing it involves checking predicate pushdown failures and missing statistics to rebalance the scan workload across nodes.

How do I localize incorrect results or crashes in StarRocks queries?

Localize incorrect StarRocks query results by selectively disabling planner and execution features. This bug localization workflow isolates the problematic feature by systematically testing feature-disable isolation across live and historical incidents.

Does this approach work for memory-heavy StarRocks queries in production?

Yes, this approach works for memory-heavy StarRocks queries in production by diagnosing excessive memory consumption. It traces cluster symptoms into a structured investigation path, identifying runtime filter issues and join blowups.