Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Managed Service for ClickHouse®
  • Getting started
    • Resource relationships
    • High availability clusters
    • Host classes
    • Networking in Managed Service for ClickHouse®
    • Quotas and limits
    • Storage
    • Backups
    • Replication
    • Coordination services
    • Dictionaries
    • Sharding
    • Maintenance
    • Managing users and access permissions
    • Supported clients
    • Memory management
    • ClickHouse® versioning policy
    • ClickHouse® settings
  • Access management
  • Pricing policy
  • Terraform reference
  • Yandex Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes

In this article:

  • Number and placement of cluster hosts
  • Single-host cluster
  • Cluster with two or more hosts
  • Multi-shard cluster
  • Storage settings
  • Maintenance settings
  • Other settings
  1. Concepts
  2. High availability clusters

High availability of a Yandex Managed Service for ClickHouse® cluster

Written by
Yandex Cloud
Updated at June 3, 2026
View in Markdown
  • Number and placement of cluster hosts
    • Single-host cluster
    • Cluster with two or more hosts
    • Multi-shard cluster
  • Storage settings
  • Maintenance settings
  • Other settings

High availability of a Managed Service for ClickHouse® cluster depends on the number and placement of its hosts, replication and sharding settings, as well as other cluster properties.

Number and placement of cluster hostsNumber and placement of cluster hosts

A Managed Service for ClickHouse® cluster consists of one or more shards, where each has one or more hosts.

Single-host clusterSingle-host cluster

A cluster with a single ClickHouse® host does not provide high availability. If the host VM fails, such a cluster will be unavailable until the VM recovery is completed. Single-host clusters are not covered by the Service level agreement (SLA).

Cluster with two or more hostsCluster with two or more hosts

The Service Level Agreement (SLA) defines a high-availability cluster as the one made up of two or more ClickHouse® hosts residing in different availability zones.

A cluster consisting of two or more hosts supports replication: ClickHouse® hosts can step in for one another as the cluster’s primary replica. Such clusters come with a dedicated coordination service, ClickHouse® Keeper or ZooKeeper, which manages replication and query distribution across hosts. You can select a coordination service when creating or updating a cluster. According to the SLA, the coordination service of a high-availability cluster must be deployed on separate hosts. A configuration where ClickHouse® and ClickHouse® Keeper share the hosts is not highly available.

A cluster may have three to five coordination service hosts. The optimal number of coordination service hosts for a highly available cluster is three. Increasing the number of ZooKeeper or ClickHouse® Keeper hosts affects cluster availability as follows:

  • As opposed to clusters with three coordination service hosts, clusters with four host have lower availability: two out of four hosts are more likely to fail than two out of three.
  • Five coordination service hosts ensure the cluster remains highly available: even if two coordination service hosts fail at the same time, this will not lead to cluster failure.

Managed Service for ClickHouse® does not support clusters with more than five coordination service hosts.

Multi-shard clusterMulti-shard cluster

Sharding improves cluster availability, but a cluster with multiple single-host shards is not highly available. According to the SLA, to ensure high availability of a sharded cluster, it should have:

  • At least two ClickHouse® hosts in each shard, located in different availability zones.
  • At least three ZooKeeper or ClickHouse® Keeper hosts located in different availability zones.

Learn more about the impact of sharding on cluster availability.

Storage settingsStorage settings

If storage runs out of space, INSERT queries, background merges, and mutations are suspended. Set up alerts in Yandex Monitoring to monitor storage usage, or enable automatic storage expansion.

Maintenance settingsMaintenance settings

Hosts may require a reboot during maintenance. A cluster consisting of a single ClickHouse® host will be unavailable during a reboot.

If a cluster consists of multiple hosts or shards, the hosts become unavailable one by one. To ensure your applications run continuously, to connect to a cluster or shard, use a special FQDN always pointing to the available host.

Learn more about maintenance.

Other settingsOther settings

Cluster availability may also be affected by:

  • Backup settings.
  • Storage disk type you selected.
  • Host classes.
  • Quotas and limits.
  • Security group setup.

ClickHouse® is a registered trademark of ClickHouse, Inc.

Was the article helpful?

Previous
Resource relationships
Next
Host classes
© 2026 Direct Cursus Technology L.L.C.