Skip to content
ClickHouse Docs
ClickHouse DocsClickHouse Docs
49.6kGet Started

concurrent_part_removal_threshold_* MergeTree table settings

View as MarkdownEdit this pageReport an issueSet up docs MCP

These settings are available in system.merge_tree_settings and are autogenerated from ClickHouse source.

concurrent_part_removal_threshold

Type
UInt64
Default
100

Activate concurrent part removal (see ‘max_part_removal_threads’) only if the number of inactive data parts is at least this.

concurrent_part_removal_threshold_for_remote_disk

Type
UInt64
Default
16
Version history
VersionDefault valueComment
26.516New setting. Lower threshold to enter the concurrent part removal path when any part being removed is on a remote disk, where each removal is typically one network round-trip. The old value (100) matches the legacy `concurrent_part_removal_threshold` default, so older `compatibility` modes preserve the previous behavior.

Same as concurrent_part_removal_threshold, but used when at least one part being removed is stored on a remote disk. The default is lower because each part removal on remote storage typically requires a network round-trip (e.g. one HTTP DELETE per part on object storage), so a serial removal of even 100 parts can stall a DROP TABLE for tens of seconds.

Navigation