All Products
Search
Document Center

ApsaraDB for ClickHouse:Create an ApsaraDB for ClickHouse cluster

Last Updated:Mar 07, 2024

This topic describes how to create an ApsaraDB for ClickHouse cluster in the ApsaraDB for ClickHouse console to help you build the desired ApsaraDB for ClickHouse cluster to meet the requirements of business expansion.

Prerequisites

  • An Alibaba Cloud account is created. For more information, see Create an account.

  • The AliyunClickHouseFullAccess permission is granted to the Resource Access Management (RAM) user that you use to create an ApsaraDB for ClickHouse cluster. For more information about how to grant permissions, see Grant permissions to a RAM user.

  • Application Real-Time Monitoring Service (ARMS) is activated before you create an ApsaraDB for ClickHouse cluster. For more information, see Activate ARMS.

Procedure

  1. Log on to the ApsaraDB for ClickHouse console.

  2. On the Clusters page, click the Default Instances tab and click Create Cluster.

  3. On the buy page, specify Billing Method.

    Billing method

    Use scenario

    Subscription

    The subscription billing method is a payment plan in which you pay a subscription fee when you purchase an ApsaraDB for ClickHouse cluster. For long-term usage, the subscription billing method is more cost-effective than the pay-as-you-go billing method. You are charged lower prices for longer subscription durations.

    Pay-as-you-go

    The pay-as-you-go billing method is a payment plan in which the system generates a bill each hour and deducts the fee from the balance of your Alibaba Cloud account based on the cluster specifications. This billing method is cost-effective for business scenarios that require access to resources for short periods of time, such as testing. You can release an ApsaraDB for ClickHouse cluster based on your business requirements to save costs. When you can estimate the amount of resources that you need each month or each year, you can change the billing method from pay-as-you-go to subscription.

  4. Set the following parameters of the ApsaraDB for ClickHouse cluster as prompted.

    Parameter

    Description

    Example

    Region

    The region where you want to create an ApsaraDB for ClickHouse cluster. After the cluster is created, the region cannot be changed. To achieve fast access, we recommend that you select a region that is nearest to the location of your business.

    China (Beijing), Singapore

    Deployment Method

    The following deployment methods are supported:

    • Single-zone: Single-zone does not support high availability.

    • Multi-zone: Multi-zone supports zone-disaster recovery that provides high availability.

    Note

    You can create an ApsaraDB for ClickHouse cluster in multiple zones only in the China (Shanghai), China (Beijing), China (Hong Kong), China (Zhangjiakou), and Singapore regions.

    Multi-zone

    Primary Zone

    Each region has multiple isolated locations known as zones. Each zone has its own independent power supply and networks. Zones in the same region do not have substantial differences.

    Beijing Zone J

    Secondary Zone

    If you select Multi-zone for Deployment Method, you must select a zone for Secondary Zone and zones must be different.

    Beijing Zone H

    Secondary Zone 2

    If you select Multi-zone for Deployment Method, you must select a zone for Secondary Zone 2 and zones must be different.

    Beijing Zone G

    Network Type

    Only a virtual private cloud (VPC) is supported. A VPC is an isolated network environment that provides enhanced security.

    VPC

    VPC.

    The VPC in which you want to create an ApsaraDB for ClickHouse cluster. If no VPC is available, go to the VPC console to create a VPC.

    vpc-bp175iuvg8nxqraf2****

    vSwitch in Primary VPC

    You must select a vSwitch in the VPC for Primary Zone. If no vSwitch is available, go to the VPC console to create a vSwitch.

    vsw-bp1gzt31twhlo0sa5****

    vSwitch for Secondary VPC

    If you select Multi-zone for Deployment Method, you must select a vSwitch in the secondary zone for vSwitch for Secondary VPC. If no vSwitch is available, go to the VPC console to create a vSwitch.

    vsw-bp16kd6ejw0dlfe8p****

    vSwitch for Secondary VPC 2

    If you select Multi-zone for Deployment Method, you must select a vSwitch in secondary zone 2 for vSwitch for Secondary VPC 2. If no vSwitch is available, go to the VPC console to create a vSwitch.

    vsw-bp1ib93rzqhdj2tjb****

    Kernel Version

    The version released by the open source community.

    21.8

    Edition

    • Single-replica Edition: For ApsaraDB for ClickHouse Single-replica Edition, a shard has only one replica. If the replica fails, the entire cluster becomes unavailable. The cluster can provide stable services only after the replica is recovered.

    • Double-replica Edition: For ApsaraDB for ClickHouse Double-replica Edition, a shard has two replicas. If a replica of the shard fails, the other replica of the shard can take over services from the failed replica.

    Note
    • If you select Multi-zone for Deployment Method, you can select only Double-replica Edition for Edition to ensure high availability.

    • The number of resources that are required by an ApsaraDB for ClickHouse cluster of Double-replica Edition is twice the number of resources that are required by an ApsaraDB for ClickHouse cluster of Single-replica Edition. An ApsaraDB for ClickHouse cluster of Double-replica Edition costs twice as much as an ApsaraDB for ClickHouse cluster of Single-replica Edition.

    • With highly reliable disks, even ApsaraDB for ClickHouse clusters of Single-replica Edition can help prevent data loss.

    Double-replica Edition

    Specification

    The CPU and memory of a single node.

    8 Cores, 32 GB

    Nodes

    The number of nodes.

    1

    Storage Type

    The type of disks. You can select the following types based on the use scenarios:

    • Enhanced SSD (ESSD)

      • Large online transaction processing (OLTP) databases: relational databases, such as MySQL, PostgreSQL, Oracle, and SQL Server databases

      • NoSQL databases: non-relational databases, such as MongoDB, HBase, and Cassandra databases

      • Elasticsearch distributed logs: Elasticsearch, Logstash, and Kibana (ELK) log analysis

    • Ultra disk

      • Development and testing

      • System disk

    ESSD PL1 (Recommended)

    Encryption Type

    Specifies whether to enable disk encryption. After disk encryption is enabled, data disks are encrypted based on block storage, and cannot be decrypted even if backup data is leaked. For more information, see Disk Encryption.

    Disk Encryption

    Service-linked Role

    If you set Encryption Type to Disk Encryption, you must assign a service-linked role to the service. This way, the service can access other cloud services.

    Created

    Encryption Key

    If you set Encryption Type to Disk Encryption, you must configure an encryption key. If no Key Management Service (KMS) key is available in the current region, go to the KMS console to create a KMS key.

    0d2470df-da7b-4786-b981-9a164dae****

    Storage Capacity

    The storage capacity of a single node. Total storage capacity = Number of nodes × Storage capacity of a single node. If the storage type is disk and the storage capacity is greater than 2,000 GB, the disk is divided into four disks, disk 0 to disk 3.

    100 GB

    Subscription Period

    If Billing Method is set to Subscription, you must specify the Subscription Period parameter.

    1 Month

    Auto-renewal

    If Billing Method is set to Subscription, you can determine whether to select auto-renewal based on your business requirements. If you did not select Auto-renewal when you created the cluster, you can perform automatic or manual renewal in the Expenses and Costs console. For more information, see Renewal.

    Auto-renewal

    Note

    When you create an ApsaraDB for ClickHouse cluster, you do not need to configure ZooKeeper specifications. After the cluster is created, 4 cores and 8 GB memory of ZooKeeper specifications are provided for free by default.

  5. After the configuration is complete, click Buy Now and complete the payment as prompted.

    Note

    It takes 1 to 10 minutes to create an ApsaraDB for ClickHouse cluster. Refresh the page to view the cluster state. If the cluster state changes from Creating to Running, the cluster is created.

Pay for the orders in the cart

If you want to purchase a subscription cluster, you can also click Add to Cart to pay for the orders in the cart in a lump sum after you complete the parameter settings. You can perform the following steps to pay for the orders in the cart:

  1. On the ApsaraDB for ClickHouse (Subscription) page, click the cart icon on the right side of the page.

  2. In the Cart panel, select the orders for which you want to pay and click Proceed to Checkout.

  3. On the Cart page, check whether the orders for which you want to pay are selected. If they are selected, click Buy Now.

    Note

    You can also specify Quantity and Subscription Cycle of ApsaraDB for ClickHouse.

  4. On the Confirm Order page, read and agree to the Terms of Service and click Pay.

  5. On the Purchase page, click Subscribe.

FAQ

Q: Why am I unable to find the cluster after I create an ApsaraDB for ClickHouse cluster?

A: The following table describes the possible causes and solutions for the failure to find the cluster.

Possible cause

Description

Solution

The selected region is invalid.

The region that you selected in the ApsaraDB for ClickHouse console is not the region in which your cluster is deployed.

In the top navigation bar of the ApsaraDB for ClickHouse console, select the region in which your cluster is deployed.

Resources are insufficient in the zone that you selected.

The system may fail to create your cluster due to insufficient resources. In this case, your payment is refunded. You can check the refund on the Orders page.

After you confirm that the payment is refunded, you can try to create an ApsaraDB for ClickHouse cluster in another zone.