Context
With most versions of XDR5+, statically configuring XDR would enable the auto-rewind feature and ship all client writes from the source to the destination. In some use cases, the auto-rewind feature may not be wanted.
You can workaround this autorewind feature by first dynamically configuring XDR and initiating a rewind of 1 second. This would update the LUT in the XDR.smd file and should prevent XDR from shipping from the beginning of time when statically configuring it afterwards.
Method
1. Dynamic creation: Please see our KB on How to Enable XDR Dynamically in Aerospike 5.0 and Later for more details
2. Issue a rewind of 1 second to update the LUT
Admin+> asinfo -v "set-config:context=xdr;dc=<DC_NAME>;namespace=<NAMESPACE>;action=add;rewind=1"
3. Add the dynamically configured XDR to your static configuration to persist changes upon a restart. Please see our documentation on XDR static and dynamic configuration for more details.
4. A rolling restart of the cluster should not cause XDR to auto-rewind from the beginning of time.