How do I install the Doris Debug Query skill?

Run npx skillmds@latest add apache/doris-debug-query in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Doris Debug Query safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Doris Debug Query?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Doris Debug Query free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Doris Debug Query?

apache (@apache) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Doris Debug Query by apache — Agent Skill

Name: Doris Debug Query
Author: apache

Doris Debug Query

Use for Apache Doris slow/hanging/timeout queries. Covers FE planner (Nereids timeout), BE Profile bottlenecks, and Exchange WaitForData / brpc E1008 on port 8060. Session vars: enable_profile, query_timeout, nereids_timeout_second.

apache b7b4d4d 4 files · 12.1 KB Updated Sep 17, 2026

File contents

Query Troubleshooting

Causes

ID	Cause	Evidence
A	Client timeout too small	`query_timeout` vs Profile wall
B	Planner	`Nereids cost too much time` / `nereids_timeout_second`
C	BE compute (scan/join/spill)	Profile active ExecTime
D	Exchange / brpc	WaitForData ≈ timeout; `failed to send brpc when exchange`; `[E1008]` on `:8060`

10 min

SET enable_profile = true;
-- reproduce

./scripts/doris-debug log-grep fe/log be/log --query-id "$QID" --pack planner
./scripts/doris-debug log-grep be/log --query-id "$QID" --pack exchange
./scripts/doris-debug audit-topk fe/log/fe.audit.log -k 20 --min-ms 5000

Planner mitigation (session only): SET disable_join_reorder=true; for fat ETL joins; fix stats with ANALYZE.

Cause C — BE compute (scan/join/spill)

When Profile shows high active ExecTime (not Wait*), route to doris-profile-reader for deep Profile analysis:

Skill routing: If doris-profile-reader is available, invoke it with the query's Profile to identify which operator (scan/join/agg/spill) dominates. Key indicators to pass:

ActiveTime per operator

RowsRead / ScanBytes for scan operators

SpillDataSize if disk spill occurred

JoinType + JoinRows for join operators

Without profile-reader, check directly:

# Get the Profile text
curl -s "http://$FE:8030/api/query_profile?query_id=$QID"

Key Profile counters for Cause C:

Counter	Meaning	Threshold
`ScannerGetBlockTime`	Time reading from storage	> 50% of ExecTime → IO bound
`SpillDataSize`	Data spilled to disk	> 0 → memory pressure, check `enable_spill`
`JoinProbeTime`	Hash join probe wall time	> 30% → check join order / type
`RowsRead` / `ScanBytes`	Scan volume	> 1B rows → check partition pruning

Profile interpretation: prefer active time over Wait*.

Cause D — Exchange / brpc

Code facts (apache/doris):

Error text in be/src/exec/operator/exchange_sink_buffer.h.
GET /api/reset_rpc_channel/{endpoints} clears brpc_internal_client_cache only (reset_rpc_channel_action.cpp).
enable_brpc_connection_check (default false) → FragmentMgr::_check_brpc_available hand_shake; consecutive failures erase internal cache.

curl -s "http://$BE:8040/api/reset_rpc_channel/all"

# be.conf — restart for static DEFINE_Bool
enable_brpc_connection_check = true
brpc_connection_check_timeout_ms = 10000

Do not trust ICMP alone. Check priority_networks.

Source

SessionVariable.java — QUERY_TIMEOUT, NEREIDS_TIMEOUT_SECOND
Profile WaitForData — exchange source operator
exchange_sink_buffer.h, reset_rpc_channel_action.cpp, fragment_mgr.cpp

---name: doris-debug-querydescription: Use for Apache Doris slow/hanging/timeout queries. Covers FE planner (Nereids timeout), BE Profile bottlenecks, and Exchange WaitForData / brpc E1008 on port 8060. Session vars: enable_profile, query_timeout, nereids_timeout_second.---# Query Troubleshooting## Causes| ID | Cause | Evidence ||----|-------|----------|| A | Client timeout too small | `query_timeout` vs Profile wall || B | Planner | `Nereids cost too much time` / `nereids_timeout_second` || C | BE compute (scan/join/spill) | Profile active ExecTime || D | Exchange / brpc | WaitForData ≈ timeout; `failed to send brpc when exchange`; `[E1008]` on `:8060` |## 10 min```sqlSET enable_profile = true;-- reproduce``````bash./scripts/doris-debug log-grep fe/log be/log --query-id "$QID" --pack planner./scripts/doris-debug log-grep be/log --query-id "$QID" --pack exchange./scripts/doris-debug audit-topk fe/log/fe.audit.log -k 20 --min-ms 5000```Planner mitigation (session only): `SET disable_join_reorder=true;` for fat ETL joins; fix stats with `ANALYZE`.## Cause C — BE compute (scan/join/spill)When Profile shows high active ExecTime (not Wait\*), route to **doris-profile-reader** for deep Profile analysis:> **Skill routing**: If `doris-profile-reader` is available, invoke it with the query's Profile to identify which operator (scan/join/agg/spill) dominates. Key indicators to pass:> - `ActiveTime` per operator> - `RowsRead` / `ScanBytes` for scan operators> - `SpillDataSize` if disk spill occurred> - `JoinType` + `JoinRows` for join operatorsWithout profile-reader, check directly:```bash# Get the Profile textcurl -s "http://$FE:8030/api/query_profile?query_id=$QID"```Key Profile counters for Cause C:| Counter | Meaning | Threshold ||---------|---------|-----------|| `ScannerGetBlockTime` | Time reading from storage | > 50% of ExecTime → IO bound || `SpillDataSize` | Data spilled to disk | > 0 → memory pressure, check `enable_spill` || `JoinProbeTime` | Hash join probe wall time | > 30% → check join order / type || `RowsRead` / `ScanBytes` | Scan volume | > 1B rows → check partition pruning |Profile interpretation: prefer active time over Wait\*.## Cause D — Exchange / brpcCode facts (apache/doris):1. Error text in `be/src/exec/operator/exchange_sink_buffer.h`.2. `GET /api/reset_rpc_channel/{endpoints}` clears **`brpc_internal_client_cache` only** (`reset_rpc_channel_action.cpp`).3. `enable_brpc_connection_check` (default false) → `FragmentMgr::_check_brpc_available` hand_shake; consecutive failures erase internal cache.```bashcurl -s "http://$BE:8040/api/reset_rpc_channel/all"``````properties# be.conf — restart for static DEFINE_Boolenable_brpc_connection_check = truebrpc_connection_check_timeout_ms = 10000```Do not trust ICMP alone. Check `priority_networks`.## Source- `SessionVariable.java` — `QUERY_TIMEOUT`, `NEREIDS_TIMEOUT_SECOND`- Profile WaitForData — exchange source operator- `exchange_sink_buffer.h`, `reset_rpc_channel_action.cpp`, `fragment_mgr.cpp`

Frequently asked questions