>>> Frank Swasey <[email protected]> schrieb am 24.05.2016 um 14:10 in >>> Nachricht <[email protected]>: > On Thu, 19 May 2016 at 3:10pm, Howard Chu wrote: > >> The contextCSN is used in replication, but it does not get replicated > itself. >> Each replica maintains its own. > > I was testing my partial replication against my test MMR setup. I have > discovered that the database suffix in the two MMR's have two contextCSN > values. The code I was using to test was checking the first contextCSN > value returned from the "master" server - which is not the "current" CSN > against the value generated by the replica. I have not (yet) figured > out what that first of the two values is indicating.
I think there is one CSN per ServerID, like this: contextCSN: 20130722065709.189194Z#000000#000#000000 contextCSN: 20160222141054.581517Z#000000#001#000000 (or another context) contextCSN: 20130719093756.074776Z#000000#000#000000 contextCSN: 20160517103616.692516Z#000000#001#000000 contextCSN: 20151007103227.123574Z#000000#002#000000 > > -- > Frank Swasey | http://www.uvm.edu/~fcs > Sr Systems Administrator | Always remember: You are UNIQUE, > University of Vermont | just like everyone else. > "I am not young enough to know everything." - Oscar Wilde (1854-1900)
