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

Re: Context CSN not updated on OpenLDAP 2.3.11

--On Friday, April 17, 2009 1:14 PM +0200 Michael Ströder <michael@stroeder.com> wrote:

Adrien Futschik wrote:
For your information, between the time OpenLDAP releases a version and
the time the projects might actually use it, is about 6-7 month. That's
because of the whole compilation/testing/validation/packaging/releasing
process that the client is using. It has been so for many year now.

I already said: The operational concept is flawed. It might not be your
fault but if you see real problems you should escalate the issue to
change that process (with the help of a request to the change management).

Another part of this that your management and/or process may be missing is the concept of point releases (2.3.32 to 2.3.43 for example) versus minor releases (2.3 to 2.4). Whereas going from one point release to another generally is backwards compatible and usually only consists of bug fixes, going between minor releases often involves incompatibilities in configuration, database structure, etc. So while the effort from going 2.3->2.4 is likely large, the effort from going to 2.3.11 or 2.3.32 to 2.3.43 is rather minute. Certainly, the effect of going between point releases in the 2.3 series has been rather well tested at this point.

As for fixes to the syncprov overlay since 2.3.11:

       Fixed slapd-bdb empty suffix and syncprov issue (ITS#4171)
       Fixed slapo-syncprov LDAP response types (ITS#4183)
       Fixed slapo-syncprov unpublished control (ITS#4238)
       Fixed slapo-syncprov message id issue
       Fixed slapo-syncprov/pcache filter dup issue (ITS#4364)
       Fixed slapo-syncprov playlog nentries reset issue (ITS#4365)
       Fixed slapo-syncprov update latency issue (ITS#4385)
       Fixed slapd syncprov/glue interaction issue (ITS#4323, ITS#4417)
       Fixed slapo-syncprov MODs cause DELs (ITS#4423)
       Fixed slapo-syncprov/syncrepl sessionlog issue (ITS#4534)
       Added slapo-syncprov extra logging
       Fixed slapo-syncprov crash under glued database (ITS#4562)
       Fixed slapo-syncprov DEL propagation bug (ITS#4589)
       Fixed slapo-syncprov need new CSN with delete syncID sets (ITS#4534)
       Fixed slapo-syncprov startup when lastmod is off (ITS#4613)
       Fixed slapo-syncprov incomplete sync on restart issues (ITS#4622)
       Fixed slapo-syncprov to complain if defined outside of a database
       Fixed slapo-syncprov presence list (ITS#4813)
       Fixed slapo-syncprov contextCSN checkpoint again (ITS#4720)
       Fixed slapo-syncprov cookie parsing error (ITS#4977)
       Fixed slapd-glue/syncprov interaction (ITS#4623)
       Fixed slapo-syncprov uninit'd vars (ITS#5048,#5049)
       Fixed slapo-syncprov refreshAndPersist race condition (ITS#5177)
       Fixed slapo-syncprov csn update with delta-syncrepl (ITS#5493)
Fixed slapo-syncprov psearch on closed connection (ITS#5401, ITS#5565)

So any number of these could be the source of the issue you are seeing and/or could be affecting your systems.



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