altinity-expert-clickhouse-part-log

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Run all queries from

checks.sql

(cluster-wide) and interpret the top offenders by rate (events/min), volume (rows/bytes), and errors.

Notes:

Default timeframes are relative (e.g., last 1h/6h/24h). Only switch to an explicit time range when the user provides one in the prompt.
Replace
```
{cluster}
```
with your ClickHouse cluster name (DataGrip).
Keep queries time-bounded (
```
event_time > now() - INTERVAL ...
```
) and use
```
LIMIT
```
.
If a query fails due to schema differences, run
```
DESCRIBE TABLE system.part_log
```
and drop only missing fields.

Cross-module triggers:

High

NewPart

rate / micro-batches → load

altinity-expert-clickhouse-ingestion

altinity-expert-clickhouse-merges

High

MutatePart

rate → load

altinity-expert-clickhouse-mutations

Many

DownloadPart

→ load

altinity-expert-clickhouse-replication

Merge saturation / slow merges → load

altinity-expert-clickhouse-merges

altinity-expert-clickhouse-storage

执行

checks.sql

中的所有查询（集群范围），并通过速率（事件/分钟）、数量（行数/字节）和错误来分析主要问题点。

注意事项：

跨模块触发条件：

高

NewPart

速率/微批量 → 加载

altinity-expert-clickhouse-ingestion

altinity-expert-clickhouse-merges

高

MutatePart

速率 → 加载

altinity-expert-clickhouse-mutations

大量

DownloadPart

→ 加载

altinity-expert-clickhouse-replication

合并饱和/合并缓慢 → 加载

altinity-expert-clickhouse-merges

altinity-expert-clickhouse-storage