From hai.zhao@gmail.com Thu May 29 03:16:52 2008 From: hai.zhao@gmail.com To: openldap-bugs@openldap.org Subject: Re: (ITS#5532) incorrect timestamp of slapd replica log Date: Thu, 29 May 2008 03:16:51 +0000 Message-ID: <200805290316.m4T3GpE5067126@boole.openldap.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4546714368621346536==" --===============4546714368621346536== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable ------=3D_Part_7580_3624331.1212031000971 Content-Type: text/plain; charset=3DUTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, Quanah: I'm considering upgrading from 2.3 to 2.4.x. I haven't test 2.4.x yet. Does this bug exist in 2.4.x too? Regards, Hai On Thu, May 29, 2008 at 1:31 AM, Quanah Gibson-Mount wrote: > --On Tuesday, May 27, 2008 10:10 AM +0000 hai.zhao(a)gmail.com wrote: > > Full_Name: Zhao Hai >> Version: 2.3.41 >> OS: Linux 2.4.21 arm >> URL: ftp://ftp.openldap.org/incoming/zhaohai-080527.patch >> Submission from: (NULL) (205.209.140.4) >> >> >> Problem: >> race condition makes incorrect timestamp in replogfile, cause certain >> modification of entries not replicate to slurp slaves. >> >> replica: 180.0.10.2:1234 >> replica: 180.0.10.3:1234 >> time: 1211855467 >> ^^^^^^^^^^ this timestamp >> >> How to reproduce the problem: >> 1) run under very slow machines (my environ: arm 266MHz) >> 2) slapd is configed to generate replogfile >> 3) ldapadd about 5 entries, then ldapmodify 2 entries without delay. >> > > This is fixed in RE23. If there is ever a 2.3.43 release, it will be in > that. In the meantime, I'd advise using 2.3.42 + your patch. > > Regards, > Quanah > > > > -- > > Quanah Gibson-Mount > Principal Software Engineer > Zimbra, Inc > -------------------- > Zimbra :: the leader in open source messaging and collaboration > ------=3D_Part_7580_3624331.1212031000971 Content-Type: text/html; charset=3DUTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, Quanah:

I'm considering upgrading from 2.3 to 2.4.x. I haven&#= 39;t test 2.4.x yet. Does this bug exist in 2.4.x too?

Regards,
Hai=

On Thu, May 29, 2008 at 1:31 AM, Quanah Gi= bson-Mount <quanah(a)zimbra.com= > wrote:
--On Tuesday, May 27, 2008 10:10 AM +0000 hai.zhao(a)gmail.com wrote:

Full_Name: Zhao Hai
Version: 2.3.41
OS: Linux 2.4.21 arm
URL: ftp://ftp.openldap.org/incoming/zhaohai-080527.patch
Submission from: (NULL) (2= 05.209.140.4)


Problem:
race condition makes incorrect timestamp in replogfile, cause certain
modification of entries not replicate to slurp slaves.

replica: 180.0.10.2:1234=
replica: 180.0.10.3:1234=
time: 1211855467
     ^^^^^^^^^^ this timestamp

How to reproduce the problem:
1) run under very slow machines (my environ: arm 266MHz)
2) slapd is configed to generate replogfile
3) ldapadd about 5 entries, then ldapmodify 2 entries without delay.

This is fixed in RE23.  If there is ever a 2.3.43 release, it will be in= that.  In the meantime, I'd advise using 2.3.42 + your patch.

Regards,
Quanah



--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration

------=3D_Part_7580_3624331.1212031000971-- --===============4546714368621346536==--