[Date Prev][Date Next]
Re: (ITS#8281) Syncrepl refresh failure when slapd is restarted midstream
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#8281) Syncrepl refresh failure when slapd is restarted midstream
- From: email@example.com
- Date: Fri, 23 Oct 2015 07:28:18 +0000
- Auto-submitted: auto-generated (OpenLDAP-ITS)
Michael Ströder wrote:
> firstname.lastname@example.org wrote:
>> Generating a new contextCSN at startup is of questionable worth. We discussed
>> this a bit 'way back in 2004
>> http://www.openldap.org/lists/openldap-devel/200408/msg00035.html Perhaps we
>> should just not do it;
>> if a single-master provider starts up empty and a
>> consumer tries to talk to it and both have an empty cookie, the provider
>> should just respond "you're up to date".
> Why not return an error to the consumer?
Typically if a consumer receives an error it will disconnect and retry later.
There's not much point making the consumer reconnect - which may be costly for
a TCP session. If it's a refreshAndPersist consumer, it just needs to hang on
and wait for some real data to arrive.
> Does the provider know whether it's running as single-master?
Generally yes. A single-master setup has serverID=0.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/