doris-debug-deployment
Skill50 starsChanged 13 days agoApache-2.0View on GitHub
Use for Doris FE/BE startup failures, port conflicts, priority_networks misrouting, meta_dir corruption, and ADD/DROP BACKEND issues.
In this repository16 other files it gives its agents.
- develop-with-evidenceSkill
- doris-architecture-advisorSkill
- doris-best-practicesSkill
- doris-debug-cloudSkill
- doris-debug-compactionSkill
- doris-debug-data-lakeSkill
- doris-debug-importSkill
- doris-debug-materialized-viewSkill
- doris-debug-nodeSkill
- doris-debug-querySkill
- doris-debug-resource-isolationSkill
- doris-debugSkill
- doris-debug-tabletSkill
- doris-pr-descriptionSkill
- doris-profile-readerSkill
- doris-repo-reviewSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 45
Default ports (from fe/conf/fe.conf and be/conf/be.conf):
- Distinctive: line 70
Check what interface BE actually bound:
- Very specific: line 90
Never remove doris-meta/ on the last healthy Master FE.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deployment & Startup
Causes
| ID | Cause | Evidence | Source anchor |
| A | Port conflict | BE/FE fail to bind; Address already in use | brpc/server.cpp, doris_main.cpp |
| B | priority_networks misconfig | brpc connection refused / wrong interface | config.cpp |
| C | meta_dir / storage_root_path not writable | Permission denied / No such file at startup | olap/olap_meta.cpp |
| D | FE metadata corruption | FE fails to start after crash; meta/image.* errors | Image.java, BDBJEJournal.java |
| E | Mixed version cluster | Protocol mismatch in thrift/brpc between FE-BE | be/src/agent/, heartbeat |
| F | DNS / hostname resolution | UnknownHostException, BE heartbeat to wrong address | Env.java frontend host check |
10 min triage
# FE status
curl -s "http://$FE:8030/api/bootstrap"
curl -s "http://$FE:8030/api/health"
# BE status
curl -s "http://$BE:8040/api/health"
# Port check
ss -tlnp | grep -E "8030|8040|8060|9030"-- Cluster membership
SHOW FRONTENDS\G
SHOW BACKENDS\GCause A — Port conflict
Default ports (from fe/conf/fe.conf and be/conf/be.conf):
| Service | Port | Config key |
| FE HTTP | 8030 | http_port |
| BE HTTP | 8040 | webserver_port |
| BE brpc | 8060 | brpc_port |
| FE MySQL | 9030 | query_port |
| FE Edit log | 9010 | edit_log_port |
# Kill stale process on target port
fuser -k 8060/tcp # BE brpc
# Then restart BECause B — priority_networks
The most common cause of "BE shows Alive=true but brpc fails." priority_networks tells BE which network interface to bind brpc to.
# be.conf — match ONE subnet exactly
priority_networks = 10.0.0.0/24Check what interface BE actually bound:
curl -s "http://$BE:8040/api/health" | grep -o '"ip":"[^"]*"'Validation: the IP in SHOW BACKENDS must be reachable from every FE and every other BE on port 8060.
Cause D — FE metadata recovery
# Check FE meta directory
ls -la fe/doris-meta/image/
ls -la fe/doris-meta/bdb/
# If bdb is corrupt and this is a follower/observer:
# 1. Remove the bad FE from the cluster
# 2. Wipe doris-meta/
# 3. Re-add as a new follower: ALTER SYSTEM ADD FOLLOWER "host:9010"Never remove doris-meta/ on the last healthy Master FE.
Source
fe/conf/fe.conf— port defaultsbe/src/common/config.cpp—priority_networksbe/src/service/doris_main.cpp— BE startupfe/.../master/Env.java— FE bootstrapfe/.../journal/bdbje/BDBJEJournal.java
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

