v.23.11Improvement

Fixed error related to parts mismatch after server restart following TRUNCATE or DROP PARTITION

Official CH changelog text
Fixed possible The local set of parts of table doesn't look like the set of parts in ZooKeeper error if server was restarted just after TRUNCATE or DROP PARTITION. #56282 (Alexander Tokmakov).
Fixed a synchronization issue where the local set of parts of a table could become inconsistent with the set of parts in ZooKeeper if the server was restarted immediately after executing TRUNCATE or DROP PARTITION commands.

Why it matters

This fix addresses a potential error that occurred when a ClickHouse server restart happened right after a TRUNCATE or DROP PARTITION operation, which could cause the local table parts to be out of sync with the metadata stored in ZooKeeper. Ensuring consistency between local parts and ZooKeeper prevents query errors and data inconsistency.

How to use it

Users benefit from this fix transparently by upgrading to the ClickHouse version that includes this patch. No changes in usage or configuration are needed.

Related resources

PreviousNext