When ClickHouse detects that data is expired, it performs an off-schedule merge. To control the frequency of such merges, you can set merge_with_ttl_timeout .
When ClickHouse see that data is expired, it performs an off-schedule merge. To control the frequency of such merges, you can set merge_with_ttl_timeout. If the value is too low, it will perform many off-schedule merges that may consume a lot of resources. If you perform the SELECT query between merges, you may get expired
11.09.2020 · If you change merge_with_ttl_timeout value using ALTER MODIFY SETTING query than you can check it using SHOW CREATE TABLE query in SETTINGS section. When you inserting "fresh" data with "old" values TTL will be executed during the first merge of these parts. It's sad, but in the old versions, we have no information about TTL in logs.
31.07.2020 · clickhouse version: 20.3.13.127 statement: ALTER TABLE {table} MODIFY SETTING merge_with_ttl_timeout=300; insert rate: 2,600,000 / sec, batched mutations: 0 The statement gets stuck and causes all the insert statements to the table to no...
18.01.2021 · As stated in documentation "Data with an expired TTL is removed when ClickHouse merges data parts. When ClickHouse see that data is expired, it performs an off-schedule merge. To control the frequency of such merges, you can set merge_with_ttl_timeout.