doris-debug-cloud
Skill50 starsChanged 13 days agoApache-2.0View on GitHub
Use for Doris storage-compute separation (cloud mode) issues: meta-service latency, cache miss storms, object store throughput, and shared-nothing config conflicts in compute groups.
In this repository16 other files it gives its agents.
- develop-with-evidenceSkill
- doris-architecture-advisorSkill
- doris-best-practicesSkill
- doris-debug-compactionSkill
- doris-debug-data-lakeSkill
- doris-debug-deploymentSkill
- 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
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 67
After bulk ingest (INSERT INTO SELECT or Stream Load), the file cache on compute BEs is cold.
- Very specific: line 91
Consider sub_file_cache for cold tables with large Parquet files — reduces S3 list/get calls.
≈ “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
Cloud (Storage-Compute Separation)
Before proceeding
Confirm cloud mode. Shared-nothing cluster commands (disk rebalance, clone, local tablet repair) are meaningless in cloud mode. Check:
SHOW FRONTENDS\G -- IsCloudMode field (Doris 3.0+)Or inspect fe.conf for cloud_unique_id or meta_service_endpoint.
Causes
| ID | Cause | Evidence | Source anchor |
| A | Meta-service latency | High P99 on SHOW PROC / DDL; meta-service RPC spikes | MetaServiceClient.java |
| B | Cache miss storm | local_cache_hit_ratio near 0; high S3 GET rate post-ingest | FileCache.cpp |
| C | Object store throughput saturation | S3 throttle errors (503 SlowDown); Throughput limit exceeded | S3FileSystem.cpp |
| D | Compute group imbalance | One compute group idle, another overloaded | ComputeGroupMgr.java |
| E | Wrong config for cloud mode | BE OOM from shared-nothing compaction knobs applied in cloud | cloud vs local config divergence |
10 min triage
-- Compute group status
SHOW COMPUTE GROUPS\G
-- File cache hit ratio (Doris 3.0+)
SELECT * FROM information_schema.file_cache_stats;# BE cache metrics
./scripts/doris-debug be-metrics --be http://$BE:8040 --grep "file_cache|local_cache"
# Object store errors in BE log
./scripts/doris-debug log-grep be/log --query-id "$QID"
grep -r "SlowDown\|503\|Throughput.*exceed" be/log/Cause A — Meta-service latency
In cloud mode, SHOW PROC and DDL go through the meta-service layer, not direct BDBJE. Latency spikes often come from:
- Meta-service RPC overload — check
meta_service_rpc_timeout_msin fe.conf SHOW PROC '/cluster_health'on a large cluster — walks every tablet via meta-service
# Check meta-service health
curl -s "http://$MS_HOST:$MS_PORT/api/health"Cause B — Cache miss storm
After bulk ingest (INSERT INTO SELECT or Stream Load), the file cache on compute BEs is cold. First query after ingest hits S3 directly — expect 3-10× latency.
-- Pre-warm cache after bulk ingest
SELECT COUNT(*) FROM new_table; -- full scan populates file cacheTune cache capacity:
# be.conf — file cache in cloud mode
file_cache_path = [{"path":"/nvme0/file_cache","total_size":536870912000,"query_limit":107374182400}]
file_cache_type = whole_file_cache # or sub_file_cache for column-levelCause C — Object store throttling
S3 has per-prefix request rate limits (~3500 PUT/GET per second per prefix). For high-concurrency cloud workloads:
# be.conf
s3_max_connections = 256 # increase parallel connections
s3_request_timeout_ms = 30000 # increase timeoutConsider sub_file_cache for cold tables with large Parquet files — reduces S3 list/get calls.
Key differences from shared-nothing
| Shared-nothing config | Cloud mode equivalent | Notes |
storage_root_path | file_cache_path | Local disk is cache only |
SHOW PROC '/backends' disk | File cache usage | Data durability is in object store |
| Clone / balance | N/A | No tablet migration |
max_tablet_version_num | Still relevant | Compaction runs on compute nodes |
compaction_* knobs | Still relevant | Tune per compute group capacity |
Source
fe/.../cloud/ComputeGroupMgr.javafe/.../cloud/MetaServiceClient.javabe/src/io/fs/s3/S3FileSystem.cppbe/src/io/cache/whole_file_cache.cppbe/src/io/cache/sub_file_cache.cpp
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.

