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

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.

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
  1. Distinctive:

    After bulk ingest (INSERT INTO SELECT or Stream Load), the file cache on compute BEs is cold.

    line 67
  2. Very specific:

    Consider sub_file_cache for cold tables with large Parquet files — reduces S3 list/get calls.

    line 91

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

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

IDCauseEvidenceSource anchor
AMeta-service latencyHigh P99 on SHOW PROC / DDL; meta-service RPC spikesMetaServiceClient.java
BCache miss stormlocal_cache_hit_ratio near 0; high S3 GET rate post-ingestFileCache.cpp
CObject store throughput saturationS3 throttle errors (503 SlowDown); Throughput limit exceededS3FileSystem.cpp
DCompute group imbalanceOne compute group idle, another overloadedComputeGroupMgr.java
EWrong config for cloud modeBE OOM from shared-nothing compaction knobs applied in cloudcloud 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:

  1. Meta-service RPC overload — check meta_service_rpc_timeout_ms in fe.conf
  2. 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 cache

Tune 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-level

Cause 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 timeout

Consider sub_file_cache for cold tables with large Parquet files — reduces S3 list/get calls.

Key differences from shared-nothing

Shared-nothing configCloud mode equivalentNotes
storage_root_pathfile_cache_pathLocal disk is cache only
SHOW PROC '/backends' diskFile cache usageData durability is in object store
Clone / balanceN/ANo tablet migration
max_tablet_version_numStill relevantCompaction runs on compute nodes
compaction_* knobsStill relevantTune per compute group capacity

Source

  • fe/.../cloud/ComputeGroupMgr.java
  • fe/.../cloud/MetaServiceClient.java
  • be/src/io/fs/s3/S3FileSystem.cpp
  • be/src/io/cache/whole_file_cache.cpp
  • be/src/io/cache/sub_file_cache.cpp

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.