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

Re: Syncrepl refreshAndPersist provider reboot

To: Thomas Hummel <thomas.hummel@pasteur.fr>, openldap-technical@openldap.org
Subject: Re: Syncrepl refreshAndPersist provider reboot
From: Quanah Gibson-Mount <quanah@symas.com>
Date: Wed, 01 Feb 2017 07:56:43 -0800
Content-disposition: inline
In-reply-to: <WM!19ef2413d37b084eca5bb7f9f30052330dbe1dcbfb3e5eaf1219948e0df4f34fca28f0de306f507af5e2f97a360ed568!@mailstronghold-2.zmailcloud.com>
References: <d3d54ecc-3738-97cc-4102-7d8358b5a1b7@pasteur.fr> <WM!19ef2413d37b084eca5bb7f9f30052330dbe1dcbfb3e5eaf1219948e0df4f34fca28f0de306f507af5e2f97a360ed568!@mailstronghold-2.zmailcloud.com>

--On Wednesday, February 01, 2017 2:05 PM +0100 Thomas Hummel<thomas.hummel@pasteur.fr> wrote:

Is this a normal behavior providing I'm using refreshAndPersist mode ?

No.

I mean do we have to restart the consumers each time the provider

restarts ?

No. But there several bugs in OpenLDAP 2.4.40 around replication, and thatrelease should be used with care if replication is involved. The Redhatbuilds of course have additional issues. YMMV.


Regards,
Quanah

--

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

Follow-Ups:
- Re: Syncrepl refreshAndPersist provider reboot
  - From: Thomas Hummel <thomas.hummel@pasteur.fr>

References:
- Syncrepl refreshAndPersist provider reboot
  - From: Thomas Hummel <thomas.hummel@pasteur.fr>

Prev by Date: Re: Script for mass updates
Next by Date: Re: Syncrepl refreshAndPersist provider reboot
Index(es):
- Chronological
- Thread