node

Diagnose StarRocks BE and FE node crashes, OOM, deadlocks, and Full GC pauses.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps diagnose and resolve StarRocks node-level incidents where BE processes crash or run out of memory, and FE nodes stall due to deadlocks, Full GC pauses, or heap leaks.

Core Features & Use Cases

  • BE failure triage: Distinguishes Linux OOM kills from internal crashes, then guides core dump review, log inspection, and memory attribution.
  • FE contention and GC analysis: Traces deadlocks with LockManager or DeadLockChecker output, and separates Full GC stalls from true FE heap exhaustion.
  • Memory leak investigation: Uses mem_tracker, memz, jstack, jmap, and audit-log analysis to identify the workload or module driving memory growth.
  • Use case: A production cluster stops responding and queries fail with version errors; this Skill narrows the issue to FE deadlock, captures the right evidence, and points to the recovery path.

Quick Start

Describe the StarRocks node symptom, and I will classify whether it is BE OOM, BE crash, FE deadlock, FE Full GC, or FE heap leak, then outline the exact checks and recovery steps.

Frequently Asked Questions about node

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

FAQPage Schema
How do I troubleshoot a StarRocks BE node out of memory crash?

To troubleshoot a StarRocks BE OOM, distinguish Linux OOM kills from internal crashes using core dump review, log inspection, and mem_tracker analysis to identify the workload driving memory growth.

Why does my StarRocks FE node stall and how do I identify a deadlock?

StarRocks FE node stalls may result from deadlocks or Full GC pauses; trace deadlocks using LockManager or DeadLockChecker output and separate true heap exhaustion from JVM garbage collection stalls.

How do I analyze jstack and core dumps to find a StarRocks memory leak?

Analyze StarRocks memory leaks by collecting jstack and core dumps, then cross-reference mem_tracker, memz, jmap, and audit-log data to attribute heap growth to specific queries or modules.

What is the best way to diagnose StarRocks FE Full GC pauses and heap growth?

Diagnosing StarRocks FE Full GC pauses involves analyzing GC logs to separate routine JVM pauses from true heap exhaustion, then inspecting memory modules to pinpoint leak sources.

Can I use audit logs to attribute StarRocks BE memory spikes to specific queries?

Yes, audit-log analysis combined with mem_tracker and memz output attributes StarRocks BE memory spikes to specific workloads or queries driving the unexpected memory growth.

What should I do when StarRocks queries fail with version errors during a node outage?

When StarRocks queries fail with version errors during an outage, narrow the issue to FE deadlock or BE OOM, capture jstack or core dump evidence, then follow the outlined recovery path.