skills.rest
Altinity
AltinityOFFICIAL
Explore all skills by this author →
WebsiteGitHub

altinity-expert-clickhouse-merges

Diagnose ClickHouse merge performance and part backlog via SQL system tables.

16|2|Updated Jan 8, 2026
Search Tags:#diagnostics#clickhouse#merges#sql-queries#database-health#part_log#cluster-monitoring
One-click install
npx skills add https://github.com/Altinity/Skills --skill altinity-expert-clickhouse-merges-altinity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: altinity-expert-clickhouse-merges
Source: https://github.com/Altinity/Skills/tree/main/altinity-expert-clickhouse/skills/altinity-expert-clickhouse-merges
Command: npx skills add https://github.com/Altinity/Skills --skill altinity-expert-clickhouse-merges-altinity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose ClickHouse merge performance, part backlog, and too many parts errors. Use for merge issues and part management problems.

Core Features & Use Cases

  • Run checks against system.merges, system.part_log, and system.parts to gauge health and backlog.
  • Identify tables with high active parts and slow merges to prioritize tuning.
  • Coordinate with related modules to optimize merges and partition management.

Quick Start

Execute the health checks against your cluster to surface merge backlog and too-many-parts issues.

Frequently Asked Questions about altinity-expert-clickhouse-merges

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose ClickHouse merge performance issues and part backlog?▼

Diagnose ClickHouse merge performance by running SQL queries against system.merges, system.part_log, and system.parts to surface merge backlog and identify tables with slow merges.

Why does ClickHouse throw too many parts errors and how can I check for them?▼

Too many parts errors occur when ClickHouse merge operations fall behind. Query system.parts and system.part_log to gauge part backlog and identify tables exceeding healthy active parts limits.

What is the best way to monitor ClickHouse database health for ongoing merge issues on a production cluster?▼

Monitor ClickHouse database health by executing SQL checks against production clusters to identify high active parts, slow merges, and part backlog for ongoing merge troubleshooting.

How do I identify which ClickHouse tables need merge tuning prioritization?▼

Identify ClickHouse tables needing merge tuning by querying system.merges and system.parts to locate tables with high active parts and slow merges that require optimization.

Can I use SQL queries to troubleshoot ClickHouse part management problems without external monitoring tools?▼

Yes, you can troubleshoot ClickHouse part management problems directly using SQL queries against system tables with built-in guardrails and safe defaults to diagnose merge bottlenecks.

Related Skills

Explore More Data & Analytics Skills→
ntk148vntk148v
42

altinity-expert-clickhouse-mutations

Diagnose ClickHouse mutation performance using system.mutations and related views.

Community
Advanced
ntk148vntk148v
42

altinity-expert-clickhouse-ingestion

Diagnose and optimize ClickHouse INSERT performance and ingestion pipelines.

Community
Advanced
duyetduyet

clickhouse-monitoring

Monitor ClickHouse clusters through the ClickHouse Monitor dashboard.

Community
Advanced
chmonitorchmonitor
255

system-tables-reference

Reference verified column names and tool mappings for ClickHouse system tables.

Official
Intermediate