altinity-expert-clickhouse-part-log

Original：🇺🇸 English

Translated

Diagnose ClickHouse issues by analyzing system.part_log (part creation, merges, mutations, downloads, removals, moves). Use for too many parts / micro-batch inserts, merge backlog or slow merges, mutation storms (ALTER DELETE/UPDATE), unusual replication DownloadPart churn, unexpected RemovePart spikes, or ZooKeeper/Keeper znode growth correlated with part activity.

3installs

Sourcealtinity/skills

Added on2026-02-11

NPX Install

npx skill4agent add altinity/skills altinity-expert-clickhouse-part-log

SKILL.md Content

View Translation Comparison →

Part Log Based Diagnostics

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

altinity-expert-clickhouse-part-log

NPX Install

Tags

SKILL.md Content

Part Log Based Diagnostics