disable_* server settings

ClickHouse server settings in the disable_* generated group.

These settings configure the ClickHouse server and are autogenerated from ClickHouse source.

disable_insertion_and_mutation

Disables INSERT, ALTER, and DELETE queries so read-only replicas do not create data parts, mutations, or merge work that affects read performance.

Writes to external storage through engines such as S3, DataLake, MySQL, PostgreSQL, and Kafka remain allowed. Background streaming from Kafka, RabbitMQ, NATS, and S3Queue tables into attached materialized views is disabled because it produces MergeTree parts and merge work on this replica.

disable_internal_dns_cache

Disables the internal DNS cache. Recommended for operating ClickHouse in systems with frequently changing infrastructure such as Kubernetes.

disable_tunneling_for_https_requests_over_http_proxy

By default, tunneling (i.e, HTTP CONNECT) is used to make HTTPS requests over HTTP proxy. This setting can be used to disable it.

• Default: false

no_proxy

By default, all requests will go through the proxy. In order to disable it for specific hosts, the no_proxy variable must be set. It can be set inside the <proxy> clause for list and remote resolvers and as an environment variable for environment resolver. It supports IP addresses, domains, subdomains and '*' wildcard for full bypass. Leading dots are stripped just like curl does.

Example

The below configuration bypasses proxy requests to clickhouse.cloud and all of its subdomains (e.g, auth.clickhouse.cloud). The same applies to GitLab, even though it has a leading dot. Both gitlab.com and about.gitlab.com would bypass the proxy.

<proxy>
    <no_proxy>clickhouse.cloud,.gitlab.com</no_proxy>
    <http>
        <uri>http://proxy1</uri>
        <uri>http://proxy2:3128</uri>
    </http>
    <https>
        <uri>http://proxy1:3128</uri>
    </https>
</proxy>