Yandex Cloud
  • Services
  • Solutions
  • Why Yandex Cloud
  • Pricing
  • Documentation
  • Contact us
Get started
Language / Region
© 2022 Yandex.Cloud LLC
Yandex Managed Service for ClickHouse
  • Getting started
  • Step-by-step instructions
    • All instructions
    • Information about existing clusters
    • Creating clusters
    • How to connect to a database
    • Stopping and starting clusters
    • SQL queries in the management console
    • Changing cluster and database settings
    • Setting up access to ObjectStorage
    • Connecting external dictionaries
    • Adding your own geobase
    • Enabling machine learning models
    • Managing data format schemas
    • Connecting to DataLens
    • Changing ClickHouse versions
    • Managing ClickHouse hosts
    • Managing ZooKeeper hosts
    • Database management
    • Managing database users
    • Managing backups
    • Managing shards
    • Managing groups of shards
    • Deleting clusters
    • Monitoring the state of a cluster and hosts
  • Practical guidelines
    • Adding data to the database
    • Sharding tables
    • Using hybrid storage
    • Getting data from Managed Service for Apache Kafka®
    • Getting data from RabbitMQ
    • Configuring Yandex Cloud DNS for cluster access from other cloud networks
    • Analyzing Object Storage logs in DataLens
  • Concepts
    • Relationship between service resources
    • Host classes
      • Active host classes
      • Archive
        • Before June 1, 2020
      • Using deprecated host classes
    • Network in Yandex Managed Service for ClickHouse
    • Quotas and limits
    • Storage types
    • Backups
    • Replication
    • Dictionaries
    • Sharding
    • Supported clients
    • ClickHouse versioning policy
    • ClickHouse settings
  • Access management
  • Pricing policy
    • Current pricing policy
    • Archive
      • Before January 1, 2019
      • From January 1 to March 1, 2019
      • From March 1, 2019 to February 1, 2020
  • API reference
    • Authentication in the API
    • gRPC
      • Overview
      • BackupService
      • ClusterService
      • DatabaseService
      • FormatSchemaService
      • MlModelService
      • ResourcePresetService
      • UserService
      • VersionsService
      • OperationService
    • REST
      • Overview
      • Backup
        • Overview
        • get
        • list
      • Cluster
        • Overview
        • addHosts
        • addShard
        • addZookeeper
        • backup
        • create
        • createExternalDictionary
        • createShardGroup
        • delete
        • deleteExternalDictionary
        • deleteHosts
        • deleteShard
        • deleteShardGroup
        • get
        • getShard
        • getShardGroup
        • list
        • listBackups
        • listHosts
        • listLogs
        • listOperations
        • listShardGroups
        • listShards
        • move
        • rescheduleMaintenance
        • restore
        • start
        • stop
        • streamLogs
        • update
        • updateHosts
        • updateShard
        • updateShardGroup
      • Database
        • Overview
        • create
        • delete
        • get
        • list
      • FormatSchema
        • Overview
        • create
        • delete
        • get
        • list
        • update
      • MlModel
        • Overview
        • create
        • delete
        • get
        • list
        • update
      • ResourcePreset
        • Overview
        • get
        • list
      • User
        • Overview
        • create
        • delete
        • get
        • grantPermission
        • list
        • revokePermission
        • update
      • Versions
        • Overview
        • list
      • Operation
        • Overview
        • get
  • Questions and answers
    • General questions
    • Questions about ClickHouse
    • Connection
    • Editing clusters
    • Cluster parameter settings
    • Moving and restoring a cluster
    • Monitoring and logs
    • All questions on the same page
  1. Concepts
  2. Relationship between service resources

Relationship between resources in Managed Service for ClickHouse

Written by
Yandex Cloud

    The main entity used in Managed Service for ClickHouse is a database cluster.

    Each cluster consists of one or more database hosts, which are virtual machines with DBMS servers deployed on them. Cluster hosts may reside in different availability zones and even different availability regions. More about the geo scope of Yandex Cloud.

    • A cluster consisting of multiple hosts has automatic failover, because the hosts can take over each other's functions as the cluster's primary replica.

      When creating such a cluster, choose one of the available mechanisms to ensure replication:

      • ClickHouse Keeper.

        The cluster will consist only of ClickHouse hosts.

      • ZooKeeper.

        The cluster will consist of ClickHouse hosts and individual ZooKeeper hosts.

    • A single-host cluster doesn't guarantee fault tolerance.

      Later you can add ZooKeeper hosts to this cluster to enable fault tolerance and replication. This will allow you to add multiple ClickHouse hosts to the cluster.

    ClickHouse Keeper or ZooKeeper hosts manage replication and distribution of queries across cluster hosts. For more information, see Replication ClickHouse.

    When creating a cluster, specify:

    • Host class: A VM template for deploying the cluster hosts. For a list of available host classes and their characteristics, see Host classes.

    • Environment: The environment where the cluster will be deployed:

      • PRODUCTION: For stable versions of your apps.
      • PRESTABLE: For testing, including the Managed Service for ClickHouse service itself. The Prestable environment is first updated with new features, improvements, and bug fixes. However, not every update ensures backward compatibility.

    You should also specify the host class when creating a shard.

    A database cluster created in a folder can be accessed by all VMs connected to the same cloud network. Learn more about networking.

    Alert

    The service can automatically access the system and diagnostic information of your databases to plot monitoring graphs and maintain the health of your cluster. The service never queries or uses the data that you saved to the database.

    Was the article helpful?

    Language / Region
    © 2022 Yandex.Cloud LLC