All four servers (master & replica) show the same contextCSN values:
dn: dc=umd,dc=edu contextcsn: 20190522130320.956183Z#000000#001#000000 contextcsn: 20190521122959.509696Z#000000#002#000000
On May 21, 2019, at 7:22 PM, Quanah Gibson-Mount quanah@symas.com wrote:
…but the consumers only processed the first change…
dn: uid=xyx,dc=umd,dc=edu entrycsn: 20190520190341.087987Z#000000#001#000000
…are failing the second change (from slapd.log):
do_syncrep2: rid=001 cookie=rid=001,sid=001,csn=20190520190418.183747Z#000000#001#000000 do_syncrep2: rid=001 CSN too old, ignoring 20190520190418.183747Z#000000#001#000000 (uid=xyz,,dc=umd,dc=edu)
This would imply they processed another change in between. What is the contextCSN in the root entry on the replicas?
// John Pfeifer Division of Information Technology University of Maryland, College Park