version-upgrade-advisor

Plan ClickHouse version upgrades with pre-upgrade checks and post-upgrade validation.

255|42|Updated Nov 16, 2023
One-click install
npx skills add https://github.com/chmonitor/chmonitor --skill version-upgrade-advisor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-upgrade-advisor
Source: https://github.com/chmonitor/chmonitor/tree/main/.agents/skills/version-upgrade-advisor
Command: npx skills add https://github.com/chmonitor/chmonitor --skill version-upgrade-advisor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of unplanned downtime, compatibility breaks, and data loss caused by unplanned or incorrect ClickHouse version upgrades, a common pain point for operators managing self-hosted or cloud ClickHouse deployments.

Core Features & Use Cases

  • Versioning Guidance: Explains ClickHouse's YY.M.patch.build versioning scheme, the difference between regular and LTS releases, and support windows to help you select the optimal target version for your stability and feature needs.
  • End-to-End Upgrade Workflow: Provides step-by-step pre-upgrade configuration and health checks, safe upgrade procedures for both single-node and replicated clusters, and post-upgrade verification steps to confirm a successful upgrade.
  • Use Case: A team running an outdated 23.3 LTS ClickHouse build can use this Skill to plan a safe upgrade to the latest 24.8 LTS, audit their current non-default settings for compatibility, and validate that replication and query performance are healthy after the upgrade.

Quick Start

Use the version-upgrade-advisor skill to plan a safe upgrade path for your ClickHouse deployment, including pre-upgrade checks and post-upgrade verification steps.

Frequently Asked Questions about version-upgrade-advisor

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

FAQPage Schema
How do I safely upgrade a ClickHouse cluster to a newer version without downtime?

To safely upgrade a ClickHouse cluster without downtime, perform pre-upgrade configuration audits, execute a rolling upgrade procedure for replicated nodes, and run post-upgrade replication and performance validation checks.

What is the difference between ClickHouse LTS and regular releases for upgrades?

ClickHouse LTS releases provide extended stability and support windows compared to regular releases, making them optimal target versions for upgrading deployments that prioritize long-term stability over immediate feature availability.

Does the ClickHouse upgrade procedure work for self-hosted Kubernetes and Docker deployments?

Yes, the ClickHouse upgrade procedure supports self-hosted deployments running on Docker, Kubernetes, bare metal, and ClickHouse Cloud, covering both single-node instances and replicated clusters with mixed version constraints.

What should I check before upgrading my ClickHouse database to prevent compatibility breaks?

Before upgrading your ClickHouse database, audit current non-default settings for compatibility, verify version support windows, and check system health to prevent unplanned downtime, compatibility breaks, and data loss.

Can I run mixed ClickHouse versions simultaneously in a replicated cluster during an upgrade?

Yes, you can run mixed ClickHouse versions in a replicated cluster during an upgrade by following structured rolling upgrade procedures that respect mixed version constraints to maintain data availability.