Sorry, but I come back with another related problem.
My problem is no longer limited to simply counting the number of records.
I have a common back-end application node that queries both the clusters in my ‘Simple Active-Active’ setup and then combines the results and sends back combined results back to the API client.
The problem, as you would know, is that I get two copies of the same record.
Q1) Is there any way in which I can have my queries on each cluster consider only the master records on that cluster?
Does Aerospike give me any customization hook just before XDR copy at the source cluster or before writing at the destination cluster so that I can set a bin in my replicated record(s) to distinguish it from the master records.
I can then filter on this bin to return only the master records.
Secondly, I am curious - for the Simple Active-Active XDR replication setup:
Q2). If, on a cluster, Aerospike does not differentiate between the master record and a record written by client, then is it possible to update the XDR copy of a record on the XDR destination cluster?
Q3) I think it is possible to have sets with same names and within same named namespaces in both the clusters.
If it is so, is it possible that 2 records in the same set, one in each cluster, have the same PK?
If that’s also true, what will happen when each of these 2 records are replicated on the other cluster… Is there a possibility of a clash of PK?