skills.rest
StarRocks
StarRocksOFFICIAL
Explore all skills by this author →
WebsiteGitHub

import

Diagnose StarRocks import slowness, timeouts, and RPC failures.

73|12|Updated Apr 24, 2026
Search Tags:#troubleshooting#import#starrocks#routine load#stream load#brpc#publish timeout
One-click install
npx skills add https://github.com/StarRocks/starrocks-debug-skills --skill import-starrocks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: import
Source: https://github.com/StarRocks/starrocks-debug-skills/tree/main/import
Command: npx skills add https://github.com/StarRocks/starrocks-debug-skills --skill import-starrocks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose StarRocks import jobs that are slow, timing out, or failing with RPC errors, so you can move from symptoms to root cause without guessing.

Core Features & Use Cases

  • End-to-end import triage: Troubleshoots Stream Load, Broker Load, Routine Load, INSERT INTO, and Flink connector issues.
  • Cause-based diagnosis: Separates write slow, publish timeout, replica sync bottlenecks, Kafka partition limits, BRPC saturation, and statistics collection conflicts.
  • Operational guidance: Uses FE transaction logs, BE thread-pool metrics, profiles, and import state tables to recommend targeted fixes.
  • Use case: A nightly load starts timing out and routine load lag grows; this Skill helps identify whether the bottleneck is source-side throughput, backend queueing, or publish-time compaction pressure.

Quick Start

Ask the Skill to analyze the import failure, correlate FE and BE evidence, and return the most likely bottleneck with the next remediation steps.

Frequently Asked Questions about import

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

FAQPage Schema
Why does StarRocks routine load lag grow and time out during nightly imports?▼

StarRocks routine load timeouts often stem from Kafka partition limits, backend queueing, or publish-time compaction pressure. Diagnosing the issue requires correlating FE transaction logs and BE thread-pool metrics to isolate whether the bottleneck is source-side throughput or internal publish delays.

How do I diagnose StarRocks stream load slowness and BRPC saturation failures?▼

To diagnose StarRocks stream load slowness and BRPC saturation failures, analyze BE thread-pool metrics and BRPC traffic alongside load state tables. This isolates write stalls and RPC bottlenecks to recommend targeted fixes for backend queueing or network saturation.

What causes publish timeout errors in StarRocks INSERT INTO and Broker Load jobs?▼

Publish timeout errors in StarRocks INSERT INTO and Broker Load jobs are typically caused by replica sync bottlenecks or statistics collection conflicts. Analyzing FE transaction logs and query profiles helps identify publish delays and compaction pressure to recommend the correct fix.

How do I troubleshoot StarRocks Flink connector write stalls and replica sync bottlenecks?▼

To troubleshoot StarRocks Flink connector write stalls and replica sync bottlenecks, gather FE transaction logs and BE thread-pool metrics to correlate write delays. Profile analysis isolates whether backend queueing or replica synchronization limits throughput and guides remediation.

Does StarRocks import diagnosis require FE transaction logs and BE thread-pool metrics?▼

Yes, diagnosing StarRocks import failures requires FE transaction logs, BE thread-pool metrics, BRPC metrics, and load state tables. These inputs are essential to isolate write stalls, publish delays, replica sync bottlenecks, and statistics collection conflicts across Stream Load, Routine Load, and Flink connector scenarios.

What is the best way to isolate StarRocks import failures caused by statistics collection conflicts?▼

The best way to isolate StarRocks import failures from statistics collection conflicts is to analyze FE transaction logs and query profiles during publish delays. This separates statistics collection conflicts from replica sync bottlenecks and Kafka partition limits to recommend the correct fix.

Related Skills

Explore More Software Engineering Skills→
StarRocksStarRocks
73

cpu-saturation

Attribute high CPU saturation on StarRocks FE or BE nodes to process, module, and workload.

Official
Advanced
esafirmesafirm
4

perfetto-trace-analysis

Analyze Perfetto traces to isolate latency, memory, and jank root causes in Android apps.

Community
Advanced
StarRocksStarRocks
73

compaction

Diagnose StarRocks compaction backlog and version-explosion failures using metrics, SQL, and logs.

Official
Advanced
fabioc-alohafabioc-aloha
1

Observability & Monitoring

Set up OpenTelemetry instrumentation for Node.js and .NET applications.

Community
Advanced