Scenario: In a 3 node cluster with replication factor 2, a node was stopped. Some updates were pushed to all the keys in a given set Down node was started again with cold start empty false. When down node was up, i connected to aerospike via aql and checked the keys of that set, and saw stale data…

Stale Data Comes Up on Node restart temporarily

meher March 21, 2017, 4:00pm 7

You may want to read about read consistency levels to understand how this works and adjust the policy on your client, or server, based on your needs:

Here are the details:

And this is one article that describes how this can be overwritten at the server level:

Topic		Replies	Views
Data consistency and reliability in aerospike Feature Discussion	6	1049	April 28, 2023
Aerospike behavior when node dies	5	4111	February 11, 2015
Aerospike Replica.RANDOM giving inconsistent result while migrations are in progress query	4	2910	October 5, 2015
Replication issue : all nodes down when synchronizing after a node restart Configuration	9	2279	November 22, 2016
Aerospike cluster behavior in different consistency mode? Configuration	6	1511	September 28, 2018