ClickHouse Coordinates a Cluster-Wide Backup with ZooKeeper
A cluster-wide backup is a ZooKeeper-coordinated election: one owner per data file, a stage barrier between phases, and a consensus loop over metadata.
All posts published on this site.
Everything published here, newest first.
A cluster-wide backup is a ZooKeeper-coordinated election: one owner per data file, a stage barrier between phases, and a consensus loop over metadata.
ClickHouse stores a per-part TTL expiry bound and removes expired rows during a merge, using a bit mask rather than a rewrite.
numbers() is a generator that iota-fills one column per block and keeps only a counter in memory.
Incremental backups reuse the base backup’s bytes: only the suffix after a verified shared prefix is uploaded, and the restore concatenates the two halves.
Keeper puts a digest of its node tree inside every Raft log entry; a follower whose recomputed digest disagrees with the leader’s kills itself.