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

Re: (ITS#8070) test023 failures

michael@stroeder.com wrote:
> This is a cryptographically signed message in MIME format.
> --------------ms080008030100090401070303
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
> quanah@zimbra.com wrote:
>> Confirmed with Howard this is a timing dependent script, and it's affec=
> ted=20
>> by recent changes to the code base.   refint used to do all its work=20
>> inline, but now it uses a separate thread, so on a slow enough machine,=
>   it=20
>> may not be done by the time the script runs its ldapsearch.
> Hmm, I'm not convinced that it really makes sense to have slapo-refint do=
> ing
> its job asynchronously.  I'm very much concerned about data consistency w=
> ith
> sync jobs relying on e.g. group membership being immediately updated etc.=
> I'd rather prefer to have slow write operations than having inconsistent
> references.  Can this be made configurable?  Please...!
> Also how about impact on transaction handling in upcoming 2.5.x?

Good questions for 2.5.

accesslog reentrancy used to be a problem, back in 2006 but other changes have been made since then to remove that obstacle. Using LDAP txns internally would also fix the backendDB reentrancy issues.

What sync jobs are you referring to? LDAP replication only promises eventual consistency; relying on instantaneous/continuous consistency here means you've got a design flaw.

> Ciao, Michael.

   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/