altinity-expert-clickhouse-replication

Name: altinity-expert-clickhouse-replication
Availability: InStock
Author: Altinity

Diagnose ClickHouse replication health with SQL scripts against system tables.

16|2|Updated Jan 8, 2026

Search Tags:#logs #latency #replication #diagnose #clickhouse #keeper #replicas

Ready to run

npx skills add https://github.com/Altinity/Skills --skill altinity-expert-clickhouse-replication-altinity

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: altinity-expert-clickhouse-replication
Source: https://github.com/Altinity/Skills/tree/main/altinity-expert-clickhouse/skills/altinity-expert-clickhouse-replication
Command: npx skills add https://github.com/Altinity/Skills --skill altinity-expert-clickhouse-replication-altinity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and remediate replication health issues in ClickHouse, including keeper connectivity, replica lag, and queue backlogs across clusters to minimize downtime and data staleness.

Core Features & Use Cases

Detect replication lag across replicas and flag read-only nodes to prevent stale reads.
Assess Keeper connectivity and queue metrics to identify bottlenecks and failure points.
Triage replication problems in production clusters and guide remediation steps.

Quick Start

Run the included SQL scripts triage.sql, queue.sql, fetches.sql, and keeper.sql against the cluster to generate actionable insights.

Frequently Asked Questions about altinity-expert-clickhouse-replication

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

FAQPage Schema

How do I diagnose ClickHouse replication lag and read-only replicas?▼

Diagnose ClickHouse replication lag and read-only replicas by running SQL scripts against system tables to surface replica lag, identify read-only nodes, and generate actionable remediation steps to minimize downtime.

What causes ClickHouse replication queue backlogs and how do I triage them?▼

Triage ClickHouse replication queue backlogs and bottlenecks by executing queue.sql and fetches.sql against system tables to assess queue metrics, identify failure points, and guide remediation.

How do I check Keeper connectivity issues in a ClickHouse cluster?▼

Check Keeper connectivity issues in a ClickHouse cluster by running keeper.sql to assess connectivity metrics, identify failure points, and guide remediation steps to resolve replication health problems.

Can I use this to detect data staleness across multiple ClickHouse replicas?▼

Yes, you can detect data staleness across multiple ClickHouse replicas by running triage.sql to identify lag scenarios, flag read-only nodes, and minimize data staleness in production clusters.

What is the best way to troubleshoot ClickHouse replication health in production?▼

The best way to troubleshoot ClickHouse replication health in production is to run SQL scripts against system tables to surface bottlenecks, keeper connectivity issues, and actionable remediation steps.