Updated at July 17, 2026 02:08 PM
Reseeding a replica
If any of a replica's write-ahead log or snapshot files are corrupted or deleted, you can reseed the replica. This procedure works only if the master's write-ahead logs are present.
-
Stop the replica using the tt stop command.
-
Delete write-ahead logs and snapshots stored in the
var/lib/<instance_name>directory. -
Start the replica using the tt start command. The replica should catch up with the master by retrieving all the master's tuples.
-
(Optional) If you're reseeding a replica after a replication conflict, you also need to restart replication.