concurrent_part_removal_threshold_* MergeTree table settings

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

concurrent_part_removal_threshold

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

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.