Context
Currently in XDR when issuing a truncate on the source cluster, the truncated records will not ship/replicate to the destination cluster.
This KB covers how to sync the destination with the source after issuing a truncate on the source cluster.
Method
Option 1: Issuing a truncate on the destination cluster
Use the timestamp in the truncate.smd file to re-run the truncate on the destination. Truncate takes a timestamp, so you should be able to get very close to within the XDR latency.
You can check the timestamp via the smd-show command. For example:
asinfo -v "smd-show:module=truncate"
Option 2: Purging the destination cluster and rewinding
- Truncate the entire namespace or specific sets that the truncate was done on
- Issue a rewind from the source to the destination to repopulate the destination. Please note that rewind is only doable with Aerospike server versions ≥ 5.0.