Server Settings

The default settings are:

```
<s3queue_log>
    <database>system</database>
    <table>s3queue_log</table>
    <partition_by>toYYYYMM(event_date)</partition_by>
    <flush_interval_milliseconds>7500</flush_interval_milliseconds>
</s3queue_log>
```

## send\_crash\_reports[​](#send_crash_reports "Direct link to send_crash_reports")

Settings for sending of crash reports to the ClickHouse core developers team.

Enabling it, especially in pre-production environments, is highly appreciated.

Keys:

|  |  |  |  |  |  |  |  |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Key Description|  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | | `enabled` Boolean flag to enable the feature, `true` by default. Set to `false` to avoid sending crash reports.| `endpoint` You can override the endpoint URL for sending crash reports.|  |  | | --- | --- | | `send_logical_errors` `LOGICAL_ERROR` is like an `assert`, it is a bug in ClickHouse. This boolean flag enables sending this exceptions (Default: `true`). | | | | | | | |

**Recommended usage**

```
<send_crash_reports>
    <enabled>true</enabled>
</send_crash_reports>
```

## series\_keeper\_path[​](#series_keeper_path "Direct link to series_keeper_path")

Path in Keeper with auto-incremental numbers, generated by the `generateSerialID` function. Each series will be a node under this path.

## show\_addresses\_in\_stack\_traces[​](#show_addresses_in_stack_traces "Direct link to show_addresses_in_stack_traces")

If it is set true will show addresses in stack traces

## shutdown\_wait\_backups\_and\_restores[​](#shutdown_wait_backups_and_restores "Direct link to shutdown_wait_backups_and_restores")

If set to true ClickHouse will wait for running backups and restores to finish before shutdown.

## shutdown\_wait\_unfinished[​](#shutdown_wait_unfinished "Direct link to shutdown_wait_unfinished")

Delay in seconds to wait for unfinished queries

## shutdown\_wait\_unfinished\_queries[​](#shutdown_wait_unfinished_queries "Direct link to shutdown_wait_unfinished_queries")

If set true ClickHouse will wait for running queries finish before shutdown.

## skip\_binary\_checksum\_checks[​](#skip_binary_checksum_checks "Direct link to skip_binary_checksum_checks")

Skips ClickHouse binary checksum integrity checks

## skip\_check\_for\_incorrect\_settings[​](#skip_check_for_incorrect_settings "Direct link to skip_check_for_incorrect_settings")

If set to true, server settings will not be checked for correctness.

**Example**

```
<skip_check_for_incorrect_settings>1</skip_check_for_incorrect_settings>
```

## snapshot\_cleaner\_period[​](#snapshot_cleaner_period "Direct link to snapshot_cleaner_period")

Period to completely remove snapshot parts for SharedMergeTree. Only available in ClickHouse Cloud

## snapshot\_cleaner\_pool\_size[​](#snapshot_cleaner_pool_size "Direct link to snapshot_cleaner_pool_size")

Threads for cleanup of shared merge tree snapshot cleaner threads. Only available in ClickHouse Cloud

## ssh\_server[​](#ssh_server "Direct link to ssh_server")

The public part of the host key will be written to the known\_hosts file
on the SSH client side on the first connect.

Host Key Configurations are inactive by default.
Uncomment the host key configurations, and provide the path to the respective ssh key to active them:

Example:

```
<ssh_server>
    <host_rsa_key>path_to_the_ssh_key</host_rsa_key>
    <host_ecdsa_key>path_to_the_ssh_key</host_ecdsa_key>
    <host_ed25519_key>path_to_the_ssh_key</host_ed25519_key>
</ssh_server>
```

## startup\_mv\_delay\_ms[​](#startup_mv_delay_ms "Direct link to startup_mv_delay_ms")

Debug parameter to simulate materizlied view creation delay

## startup\_scripts.throw\_on\_error[​](#startup_scripts.throw_on_error "Direct link to startup_scripts.throw_on_error")

If set to true, the server will not start if an error occurs during script execution.

## storage\_configuration[​](#storage_configuration "Direct link to storage_configuration")

Allows for multi-disk configuration of storage.

Storage configuration follows the structure:

```
<storage_configuration>
    <disks>
        <!-- configuration -->
    </disks>
    <policies>
        <!-- configuration -->
    </policies>
</storage_configuration>
```

### Configuration of disks[​](#configuration-of-disks "Direct link to Configuration of disks")

Configuration of `disks` follows the structure given below:

```
<storage_configuration>
    <disks>
        <disk_name_1>
            <path>/mnt/fast_ssd/clickhouse/</path>
        </disk_name_1>
        <disk_name_2>
            <path>/mnt/hdd1/clickhouse/</path>
            <keep_free_space_bytes>10485760</keep_free_space_bytes>
        </disk_name_2>
        <disk_name_3>
            <path>/mnt/hdd2/clickhouse/</path>
            <keep_free_space_bytes>10485760</keep_free_space_bytes>
        </disk_name_3>
        ...
    </disks>
</storage_configuration>
```

The sub-tags above define the following settings for `disks`:

|  |  |  |  |  |  |  |  |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Setting Description|  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | | `<disk_name_N>` The name of the disk, which should be unique.|  |  |  |  | | --- | --- | --- | --- | | `path` The path to which server data will be stored (`data` and `shadow` catalogues). It should end with `/`| `keep_free_space_bytes` Size of the reserved free space on disk. | | | | | | | |

Note

The order of the disks does not matter.

### Configuration of policies[​](#configuration-of-policies "Direct link to Configuration of policies")

The sub-tags above define the following settings for `policies`: