Unfortunately, we dont have such option today. But we want to provide CP mode in the future with the behavior that you just mentioned. However, there are no immediate plans of doing this. So, you cannot bank on this feature for the short term.
By default, our clients send the read requests also to master. So, in a normal situation, the read should not even go to node B. If at all the read request goes to node B, I can think of an extreme scenario where it can read different value. It is a race condition between readers and writers. The writer comes and updates node A, its yet to replicate to B. Before the replication to B is over if the client comes and does a read from both the nodes, it will get different values. This is because Aerospike by default provides only “committed read” (isolation level-1).
You can overcome this sitation, if you are willing to pay the cost and think “repeatable read” is more important for you. The clients API takes “consistency level” as a parameter in the policy (Ref java doc). If you choose consistency level as “all”, then all the replicas are consulted for every read and the latest one will be returned. Obviously, there is a higher cost to pay for this.