Skip to main content

Manage versions in Aiven for ClickHouse®

Aiven for ClickHouse® supports multiple ClickHouse versions. You can select a version when creating a service and upgrade the service to a newer supported version later.

Supported ClickHouse versions

Aiven for ClickHouse currently supports the following versions:

  • 25.3 (default)
  • 25.8

If you do not specify a version when you create a service, the platform uses the default version.

Before you upgrade

Before upgrading your service, complete the following checks:

  • Review the upstream ClickHouse release notes.
  • Test the upgrade in a development or staging environment by forking the service and upgrading the fork first.
  • Verify that your applications and clients support the target version.
  • Ensure recent backups are available.

Downgrading to an earlier ClickHouse version is not supported.

How upgrades work

During a version upgrade, the platform replaces the service nodes with new nodes running the selected version.

  • New service nodes are created with the selected ClickHouse version.
  • The new nodes start alongside the existing nodes.
  • Data is streamed from the existing nodes to the new nodes.
  • Once the migration completes, the service switches to the upgraded nodes.
  • The previous nodes are removed.

This process avoids modifying the existing nodes directly during the upgrade.

Upgrade your service

Upgrade a service to a newer supported ClickHouse version using the Aiven Console, CLI, API, or Terraform.

  1. In the Aiven Console, open your Aiven for ClickHouse service.
  2. On the Overview page, go to the Maintenance section.
  3. Click Actions > Upgrade version.
  4. Select a version to upgrade to, and click Upgrade.