v.24.3Experimental Feature

Change in Zero-Copy Replication: Dropping Table Requires Removing Related Locks and Directory

Official CH changelog text
A change for the "zero-copy" replication: all zero copy locks related to a table have to be dropped when the table is dropped. The directory which contains these locks has to be removed also. #57575 (Sema Checherinda).
Improved zero-copy replication by ensuring all zero-copy locks and their directories are removed when a table is dropped.

Why it matters

This feature resolves issues where zero-copy locks persisted after dropping a table, potentially causing stale lock conflicts and resource leaks. By automatically dropping all related locks and removing their directories, it ensures a cleaner and more reliable replication cleanup.

How to use it

Users benefit from this feature automatically when dropping tables involved in zero-copy replication. No additional configuration is required; zero-copy locks and their corresponding directories are cleaned up as part of the table drop operation.

Related resources

PreviousNext