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

Re: contextCSN values and MMR

Quanah Gibson-Mount wrote:
> On Aug 11, 2013, at 7:41 AM, Michael Ströder <michael@stroeder.com> wrote:
>> Quanah Gibson-Mount wrote:
>>> On Aug 10, 2013, at 12:01 PM, Quanah Gibson-Mount <quanah@zimbra.com> wrote:
>>>> On Aug 10, 2013, at 11:08 AM, Michael Ströder <michael@stroeder.com> wrote:
>>>>>> On Sat, 10 Aug 2013, Michael Ströder wrote:
>>>>>>> Are contextCSN values on all replicas really in sync if changes were correctly
>>>>>>> replicated?
>>>>>>> I've implemented a monitoring check used with normal MMR setup (OpenLDAP
>>>>>>> 2.4.35, own build on Debian Squeeze) which also checks the contextCSN values
>>>>>>> on all replicas compared by server-id.
>>>>>>> Sometimes we observe, even in isolated tests, that contextCSN values for a
>>>>>>> certain server-id differ for quite a while (up to hours) even though the
>>>>>>> changes coming from that server were definitely replicated to all other
>>>>>>> replicas. After a while the contextCSN values get suddenly updated.
>>>>>>> Unfortunately this does not always happen.
>>>>>>> Any hint is highly appreciated.
>>>> [..]
>>>> I always set the syncprov checkpoint on all servers, replicas or masters.
>>> Correction. I load slapo-syncprov on all replicated db backends. I don't set the checkpoint.
>> As said this is a MMR setup
>> => slapo-syncprov is loaded on all replicated DB backends
>> Anythings else why contextCSN is not updated?
> Doesn't happen to me with delta-syncrepl based MMR. 

Are you continously comparing the contextCSN values with a monitoring component?

Ciao, Michael.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature