Changing cluster settings

If you don't have the Yandex.Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

To change the host class for the cluster:

1. View a description of the CLI's update cluster command:

   $ yc managed-clickhouse cluster update --help
   

2. Request a list of available host classes (the ZONES column specifies the availability zones where you can select the appropriate class):

   $ yc managed-clickhouse resource-preset list
   
   +-----------+--------------------------------+-------+----------+
   |    ID     |            ZONE IDS            | CORES |  MEMORY  |
   +-----------+--------------------------------+-------+----------+
   | s1.nano   | ru-central1-a, ru-central1-b,  |     1 | 4.0 GB   |
   |           | ru-central1-c                  |       |          |
   | s1.micro  | ru-central1-a, ru-central1-b,  |     2 | 8.0 GB   |
   |           | ru-central1-c                  |       |          |
   | ...                                                           |
   +-----------+--------------------------------+-------+----------+
   

3. Specify the class in the update cluster command:

   $ yc managed-clickhouse cluster update <cluster name>
        --clickhouse-resource-preset <class ID>
   

   Managed Service for ClickHouse will run the update host class command for the cluster.

   You can change the ZooKeeper host class using a similar parameter: --zookeeper-resource-preset.

If you don't have the Yandex.Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

To increase the storage size for a cluster:

1. Make sure the required cluster is using network storage (it is not yet possible to increase the size of local storage). To do this, request information about the cluster and find the disk_type_id field: it should be set to network-hdd or network-ssd:

   $ yc managed-clickhouse cluster get <cluster name>
   
   id: c7qkvr3u78qiopj3u4k2
   folder_id: b1g0ftj57rrjk9thribv
   ...
   config:
     clickhouse:
       resources:
         resource_preset_id: s1.nano
         disk_size: "21474836480"
         disk_type_id: network-ssd
   ...
   

2. View a description of the CLI's update cluster command:

   $ yc managed-clickhouse cluster update --help
   

3. Make sure the cloud's quota is sufficient to increase the storage size: open the Quotas page for your cloud and check that the Yandex Managed Service for ClickHouse section still has space available in the space line.

4. Specify the required amount of storage in the update cluster command (it must be at least as large as disk_size in the cluster properties):

   $ yc managed-clickhouse cluster update <cluster name>
        --clickhouse-disk-size <storage size in GB>
   

   If all these conditions are met, Managed Service for ClickHouse launches the operation to increase storage space.

   You can change the storage size for ZooKeeper by using the same parameter, --zookeeper-disk-size.

1. Go to the folder page and select Managed Service for ClickHouse.

2. Select the cluster and click Edit cluster in the top panel.

3. Change additional cluster settings:

• Backup start (UTC): The time in UTC when you want to start creating a backup of a cluster (in 24-hour format).

• Access from the management console: Select this option to be able to execute SQL queries to cluster databases from the Yandex.Cloud management console.

• Access from Yandex.Metrica and AppMetrica: Select this option to be able to export data from AppMetrica to a cluster.

1. Change the DBMS settings by clicking Configure under DBMS settings:

   • Geobase uri: Address of the archive with the user geobase in Object Storage.

   • Keep alive timeout: Amount of time in seconds after the last request to ClickHouse, during which the server waits for a new request. If no requests are received during this time, ClickHouse breaks the connection. To learn more, see the ClickHouse documentation.

   • Log level: Event logging level. At each next level, the log will contain complete information from the previous one:

     1. ERROR: Information about errors in the cluster.
     2. WARNING: Information about events that may cause errors in the cluster.
     3. INFORMATION: Confirmations, information about events that don't lead to errors in the cluster.
     4. DEBUG: System information for later use in debugging.
     5. TRACE: All available information about the cluster performance.

     To learn more about the log levels, see the ClickHouse documentation.

   • Mark cache size: Approximate size (in bytes) of the cache of marks used by MergeTree table engines. The cache is shared by the server and the memory is allocated as needed. To learn more about logging in ClickHouse, see the documentation.

   • Max concurrent queries: Maximum number of queries processed simultaneously. To learn more, see the ClickHouse documentation.

   • Max connections: Maximum number of inbound connections. To learn more, see the ClickHouse documentation.

   • Max partition size to drop: Maximum size (in bytes) of a partition in a MergeTree table, which you can delete using the DROP query.

   • Max table size to drop: Maximum size (in bytes) of a MergeTree table which you can delete using the DROP query. If 0, you can delete all tables without restrictions. To learn more, see the ClickHouse documentation.

   • Timezone: Server time zone. Specified by the IANA identifier as the UTC time zone or geographical location (for example, Africa/Abidjan). To learn more, see the ClickHouse documentation.

   • Uncompressed cache size: Cache size in bytes for uncompressed data used by MergeTree table engines. To learn more, see the ClickHouse documentation.

   • Compression: Rules for compressing data in MergeTree tables.

     • Method: Compression method. Two methods are available: LZ4 and zstd.
     • Min part size: Minimum size (in bytes) of a data part in a table. ClickHouse only applies the rule to tables with data parts greater than or equal to the Min part size value.
     • Min part size ratio: Minimum table part size to total table size ratio. ClickHouse only applies the rule to tables in which this ratio is greater than or equal to the Min part size ratio value.

     You can add several compression rules. ClickHouse checks the Min part size and Min part size ratio conditions and applies the rules to those tables that meet both of them. If multiple rules can be applied to the same table, ClickHouse applies the first of them. If none of the rules are applicable, ClickHouse uses the LZ4 compression method. To learn more, see the ClickHouse documentation

   • Graphite rollup: GraphiteMergeTree engine configurations for thinning and aggregating/averaging (rollup) Graphite data. You can set up multiple configurations and use them for different tables.

     To learn more about Graphite support in ClickHouse, see the documentation.

     • Name: Configuration name.
     • Patterns: Set of thinning rules. A rule applies if the metric name matches the Regexp parameter value and the age of data matches the Retention parameter group value.
       • Function: Aggregation function name.
       • Regexp: Regular expression that the metric name must match.
       • Retention: Retain parameters. The function applies to data whose age is in the [Age, Age + Precision] range. You can set several groups of these parameters.
         • Age: Minimum data age in seconds.
         • Precision: Accuracy of determining the age of the data in seconds. Must be a divisor for 86,400 (the number of seconds in 24 hours).

   • Merge tree: MergeTree engine configuration. To learn more, see the ClickHouse documentation

     • Max bytes to merge at min space in pool: Maximum total size of a data part to merge when the number of free threads in the background pool is minimum.
     • Max replicated merges in queue: Maximum number of merge tasks that can be in the ReplicatedMergeTree queue at the same time.
     • Number of free entries in pool to lower max size of merge: Threshold value of free entries in the pool. If the number of entries in the pool falls below this value, ClickHouse reduces the maximum size of a data part to merge. This helps handle small merges faster, rather than filling the pool with lengthy merges.
     • Parts to delay insert: Number of active data parts in a table, on exceeding which ClickHouse starts artificially reduce the rate of inserting data into the table.
     • Parts to throw insert: Threshold value of active data parts in a table, on exceeding which ClickHouse throws the 'Too many parts ...' exception.
     • Replicated deduplication window: Number of recent hash blocks that ZooKeeper will store (the old ones will be deleted).
     • Replicated deduplication window seconds: Time during which ZooKeeper stores the hash blocks (the old ones wil be deleted).

2. Click Save changes.