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

Re: Replication delay



El 22/3/19 a las 17:19, Michael Ströder escribió:

     Checking contextCSN attribute of all ldap servers. I get something
like this:

contextCSN: 20190322064915.077600Z#000000#01f#000000
contextCSN: 20190322065006.637604Z#000000#020#000000
contextCSN: 20190322065002.859879Z#000000#021#000000
contextCSN: 20190322065000.303715Z#000000#022#000000
contextCSN: 20190301102558.398349Z#000000#027#000000
contextCSN: 20190314080533.305657Z#000000#029#000000

     There is one value for every server. When everything is ok, these
values are the same in all servers. But sometimes in the new server are
different, with values older than the in the others.

This is most times caused by an OpenLDAP bug. I see this quite often
with MMR providers even though the entries have been correctly
replicated to the other providers. Hence I asked for your detection method.

I don't know if there is or not a bug related with this (I didn't have any false alert for my running farm), but when I have this alert, then I checked for latest changes (got from accesslog) and they aren't replicated. So the delay is really happening.

--
Angel L. Mateo Martínez
Sección de Telemática
Área de Tecnologías de la Información
y las Comunicaciones Aplicadas (ATICA)
http://www.um.es/atica
Tfo: 868889150
Fax: 868888337