Why do I see years of lag after enabling XDR

Problem Description

After enabling XDR statically for the first time, the XDR lag metric shows that there are years of lag.

Admin+> info xdr
~~~~~~~~~~~~~~~~~~~XDR Information dc2 (2026-01-27 18:17:00 UTC)~~~~~~~~~~~~~~~~~~~~
      Node|Success|~~~~~~~~Retry~~~~~~~~~|Recoveries|         Lag|    Avg|Throughput
          |       |Connection|Destination|   Pending|  (hh:mm:ss)|Latency|   (rec/s)
          |       |     Reset|           |          |            |   (ms)|          
dc1-1:3000|      0|         0|          0|      4096|140898:16:57|      0|         0
          |       |          |           |      4096|            |     --|          
Number of rows: 1

Explanation

When enabling XDR statically for the first time or when doing a full rewind, it is expected behavior to see XDR lag in years. This is because we would be shipping all records from the beginning of Aerospike time.

In the example above, we can see that XDR lag is 140898:16:57 = 16 years. In 2026, this is around how long Aerospike has been around for. The lag should decrease to 0 when recoveries_pending reaches 0.

Solution

Monitor recoveries_pending and check that it goes down to 0. Once it reaches 0, the rewind should be finished.

Applies To Earliest Version

Applies To Latest Version