Back to Details

altinity-expert-clickhouse-part-log

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Part Log Based Diagnostics

基于Part Log的诊断

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
中的所有查询（集群范围），并通过速率（事件/分钟）、数量（行数/字节）和错误来分析主要问题点。
注意事项：
  • 默认时间范围为相对时间（例如，最近1小时/6小时/24小时）。仅当用户在提示中提供明确时间范围时才切换为该范围。
  • 将
    {cluster}
    替换为你的ClickHouse集群名称（DataGrip中）。
  • 保持查询有时间限制（
    event_time > now() - INTERVAL ...
    ）并使用
    LIMIT
    。
  • 如果查询因架构差异失败，执行
    DESCRIBE TABLE system.part_log
    并仅删除缺失的字段。
跨模块触发条件：
  • 高
    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