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

Re: Replication delay

To: openldap-technical@openldap.org
Subject: Re: Replication delay
From: "Angel L. Mateo" <amateo@um.es>
Date: Fri, 22 Mar 2019 09:55:49 +0100
Content-language: es-ES
In-reply-to: <1F498BFC7CC5093D7B4F5331@[192.168.1.39]>
References: <3b8a1ac0-43ac-f7a4-ad4b-5b87554a2d5c@um.es> <8C2D61BDD4E0278596565183@[192.168.1.39]> <c3c12973-44fd-cbe4-9c51-4ea296086e26@um.es> <1F498BFC7CC5093D7B4F5331@[192.168.1.39]>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1

El 21/3/19 a las 22:51, Quanah Gibson-Mount escribió:

The first thing you should look at is if there are any instances ofREFRESH in your logs, something along the lines of:
do_syncrep2: rid=001 delta-sync lost sync, switching to REFRESH
If you see that, the issue isn't delayed replication, the issue is thatyour databases are out of sync.

Yesterday I had delays with replication and there was the refresh logsI have already sent.

But now I'm having delays again (since 10min), but I don't have anyrefresh log.


--
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

Follow-Ups:
- Re: Replication delay
  - From: Quanah Gibson-Mount <quanah@symas.com>

References:
- Replication delay
  - From: Ángel L. Mateo <amateo@um.es>
- Re: Replication delay
  - From: Quanah Gibson-Mount <quanah@symas.com>
- Re: Replication delay
  - From: Ángel L. Mateo <amateo@um.es>
- Re: Replication delay
  - From: Quanah Gibson-Mount <quanah@symas.com>

Prev by Date: Re: Replication delay
Next by Date: Re: Replication delay
Index(es):
- Chronological
- Thread