conflict-resolution-policy seems vital for when we have counters on Aerospike and sporadically cold-restarts are required.
Since “generation” mode has a limit of 65k and then it goes back to zero passed that value, when making a cold restart of highly updated records inside Aerospike it is very likely to produce outdated records.
My question is: is there any downside on using TTL conflict-resolution-policy?
One thing I can think is that “generation” works for every namespace configuration but TTL conflict-resolution works only when the namespace has a TTL defined. But we need to change this value in our production environment, so I’d like to know if I’m missing something else.
Thanks a lot!