Re: (ITS#9015) Replication goes haywire querying promoted master

[ondra@mistotebe.net]

On Wed, Apr 24, 2019 at 01:30:18PM +0000, ondra@mistotebe.net wrote:
> On Tue, Apr 23, 2019 at 11:28:40PM +0000, quanah@symas.com wrote:
>> The consumer did not replicate the database as a part of the initial
>> search, so I don't think it qualifies as "up to date".  I.e., it's primary
>> DB remains empty.
> 
> Ah, that wasn't mentioned, my assumption was that the source DB was
> actually empty.
> 
> This is coming from ITS#8281 fix in cd8ff37629012c1676ef79de164a159da9b2ae89.

I've pushed a change that makes sure we end up with a contexCSN,
generating one if necessary whenever we're configured to be a master
(olcMirrorMode is set or no olcSyncrepl exists) here:
https://github.com/mistotebe/openldap/tree/its9015

It's kind of a followup on this (reverting part of ITS#8281 above):
https://www.openldap.org/lists/openldap-devel/201904/msg00015.html

-- 
OndÅ?ej Kuzník
Senior Software Engineer
Symas Corporation                       http://www.symas.com
Packaged, certified, and supported LDAP solutions powered by OpenLDAP