FAQ - Why am I seeing records filtered out on a rewind when I don't have an XDR filter

Detail

With bin convergence enabled, why do I see records filtered out on a rewind when I don’t have an XDR filter?

Admin+> asinfo -v "set-config:context=xdr;dc=dc4;namespace=test;action=add;rewind=all"
dc3-1:3000 (10.88.0.3) returned:
ok

10.88.0.6:3000 (10.88.0.6) returned:
ok

10.88.0.5:3000 (10.88.0.5) returned:
ok

10.88.0.4:3000 (10.88.0.4) returned:
ok

Admin+> show stat xdr like filter -flip
~XDR Statistics dc4 (2025-09-04 18:04:24 UTC)~
          Node|filtered_out
10.88.0.4:3000|         118
10.88.0.5:3000|         112
10.88.0.6:3000|         128
dc3-1:3000    |         142
Number of rows: 4

Answer

As bin shipping is based on bin LUTs, with bin convergence, XDR writes may bring in bins with older LUTs than the last ship time. Therefore, the source cluster we are doing the rewind from would filter out any XDR written records when performing the rewind.

Applies To Earliest Version

Applies To Latest Version