Re: difference in multi-master replication since 2.4.57

> --On Wednesday, March 3, 2021 6:24 PM +0100 Emmanuel Seyman > <emmanuel(a)seyman.fr&gt; wrote: > >> The problem is that I don't see any messages in the log that stand >> out as being errors (granted, I'm not sure what I'm looking for). >> In fact, the alert flaps every once in a while as the two nodes >> come back in sync and drift away from each other again. >> >> I find these values surprising considering I've never seen a syncrepl >> error in the 2 years before the upgrade. Is there a known issue with >> replication in 2.4.57 that would explain these sync differences? My slapdcheck package [1] also implements exactly this check and sometimes it shows a difference although the changes have been corrected replicated (normal syncrepl). You can look at the code to verify what it's doing: https://gitlab.com/ae-dir/slapdcheck/-/blob/master/slapdcheck/__init__.py... (It reads the actual syncrepl providers from cn=config before comparing the contextCSN values for each serverID.) I discussed this several times with Howard and Ondrej but no idea came up why that happens.