[Date Prev][Date Next] [Chronological] [Thread] [Top]

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

--On Tuesday, April 23, 2019 8:56 PM +0200 Ond=C5=99ej Kuzn=C3=ADk=20
<ondra@mistotebe.net> wrote:

> Going by what I think I remember of the consumer code did:
> - on set up, it finds out there's no cookie to go by so it goes into
>   refresh on the main DB
> - main DB responds with success but no/empty cookie
> - consumer starts over but again finds itself with no cookie, so it goes
>   to step one
>
> But the consumer is actually up to date at that point as the search
> suggested, so it should just go ahead and do the refreshAndPersist on
> accesslog as it planned to originally. And as operations hit the main
> DB, they will replicate accordingly, even if that were to happen after
> the original search and before this one[0].

The consumer did not replicate the database as a part of the initial=20
search, so I don't think it qualifies as "up to date".  I.e., it's primary=20
DB remains empty.

--Quanah



--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>