Skip to main content
These settings configure the ClickHouse server and are autogenerated from ClickHouse source.

​
use_minimalistic_part_header_in_zookeeper

Obsolete setting, does nothing. Replicated tables always store the header of a data part compactly in a single znode. Part headers written by older versions with separate columns and checksums child znodes are still read.

​
use_separate_cache_arena

Enable a dedicated jemalloc arena for cache allocations (mark cache, uncompressed cache, page cache). Isolates cache data from query-processing allocations, reducing memory fragmentation.

​
use_shared_merge_tree_log_pipeline

Only available on ClickHouse Cloud. When enabled, system.*_log tables are backed by SharedMergeTree via an S3-based pipeline. For each log <log>, the following objects are created automatically on startup:
  • system.<log>_s3 — an S3-backed table that is the direct flush target; each SYSTEM FLUSH LOGS call writes a new partitioned file here.
  • system.<log>_s3queue — an S3Queue table (ordered mode) that picks up files from <log>_s3 and streams rows downstream. Each node processes only its own files via partition_regex-based partitioning.
  • system.<log>_mv — a MATERIALIZED VIEW that routes rows from <log>_s3queue into the final SharedMergeTree table.
  • system.<log> — the final SharedMergeTree table where rows accumulate and are queried.
On schema or settings change, the affected table is renamed to <log>_0, <log>_1, etc. and recreated, consistent with the existing SystemLog rotation behavior. Requires <shared_log_pipeline><endpoint> to be set in the server configuration. See also: shared_log_pipeline.enable_sync_flush, shared_log_pipeline.flush_timeout_seconds.
Last modified on October 7, 2026