Automating Data Expiration in ClickHouse with TTL on MergeTree Tables
Guide to configuring ClickHouse TTL on MergeTree tables for automatic row expiration, including steps, verification, and recovery.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Guide to configuring ClickHouse TTL on MergeTree tables for automatic row expiration, including steps, verification, and recovery.
Context Moleculer's built-in cache pattern relies on per-node TTL expiration. When services scale horizontally, each node maintains its own cache instance with independent timers. The framework does not ship with a native cross-node invalidation mechanism, so a cache entry that expires on one node may remain valid on another until its local TTL elapses. Goal
When designing a caching layer with memcached, the goal is to guarantee that a key expires at the same instant for all application instances, regardless of the time zone in which each client runs. The memcached server interprets an expiration value: numbers below 2 592 000 seconds are treated as a relative TTL (seconds from the current server time), while va