agentleFS
apacheapache/doris-skills/skills/doris-debug/deployment/SKILL.md

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.

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
  1. Very specific:

    Default ports (from fe/conf/fe.conf and be/conf/be.conf):

    line 45
  2. Distinctive:

    Check what interface BE actually bound:

    line 70
  3. Very specific:

    Never remove doris-meta/ on the last healthy Master FE.

    line 90

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Deployment & Startup

Causes

IDCauseEvidenceSource anchor
APort conflictBE/FE fail to bind; Address already in usebrpc/server.cpp, doris_main.cpp
Bpriority_networks misconfigbrpc connection refused / wrong interfaceconfig.cpp
Cmeta_dir / storage_root_path not writablePermission denied / No such file at startupolap/olap_meta.cpp
DFE metadata corruptionFE fails to start after crash; meta/image.* errorsImage.java, BDBJEJournal.java
EMixed version clusterProtocol mismatch in thrift/brpc between FE-BEbe/src/agent/, heartbeat
FDNS / hostname resolutionUnknownHostException, BE heartbeat to wrong addressEnv.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\G

Cause A — Port conflict

Default ports (from fe/conf/fe.conf and be/conf/be.conf):

ServicePortConfig key
FE HTTP8030http_port
BE HTTP8040webserver_port
BE brpc8060brpc_port
FE MySQL9030query_port
FE Edit log9010edit_log_port
# Kill stale process on target port
fuser -k 8060/tcp  # BE brpc
# Then restart BE

Cause 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/24

Check 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 defaults
  • be/src/common/config.cpp — priority_networks
  • be/src/service/doris_main.cpp — BE startup
  • fe/.../master/Env.java — FE bootstrap
  • fe/.../journal/bdbje/BDBJEJournal.java

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.