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

Re: contextCSN attribute update on replication


On Wed, Aug 10, 2016 at 9:33 PM, Michael Ströder <michael@stroeder.com> wrote:
Quanah Gibson-Mount wrote:
> --On Wednesday, August 10, 2016 12:45 AM +0200 Michael Ströder
> <michael@stroeder.com> wrote:
>
>>> Didn't we have a discussion about why one should run the syncprov
>>> overlay on all nodes a while back?
>>
>> Yes, and since then it is enabled on all replicas. Still this issue
>> happens.
>
> Interesting... I haven't run replica only nodes in a while.  Maybe someday I'll
> be able to work on OpenLDAP again.

The point is that not read-only consumers have the issue with contextCSN. It's
rather one or another of the MMR providers.

Ciao, Michael.

Thank you so much for your answers.
We also have syncprov overlay running on the slave servers too.

We will have to live with this issue then:

* We have adapted our nagios script so that it now checks both contextCSN and last modified entry's entryCSN values in order to know if slave replication is working ok.

* We are also checking on cn=Tasklist,cn=Threads,cn=Monitor if the replication thread is running (do_syncrepl) in the slaves.

Thanks again for your help.

Regards,


Oscar Remírez de Ganuza Satrústegui
IT Services
Universidad de Navarra
Tel. +34 948425600 x803130
http://www.unav.edu/web/it/