openldap-devel April 2014

openldap-devel@openldap.org

4 participants
5 discussions

LMDB stuff
by Howard Chu 02 May '14

02 May '14

Was chatting with Emmanuel Lecharny (who is currently working on Mavibot for ApacheDS, an MVCC backend similar to LMDB) and had an interesting realization: we can avoid the current issue of long-lived reader txns preventing page reclamation. The key point is this - currently for any txn, we store in the freeDB a list of the pageIDs that were freed in that txn (due to being copied or deleted). All we need is to know that any of these pages has been copied *twice* since the txn of the outstanding reader. At that point, any such page is so new that the reader would never have seen it, and if no other readers are outstanding then the page can be safely reclaimed. Currently mavibot maintains this revision history in a dedicated Btree (much like our freeDB but with more info contained). I'm thinking, since we're already going to add a txnID to every page's page header, we can simply add a 2nd txnID, recording the txnID of the previous change to this page's ancestor. Then, any page where this prevTxnID is >= the outstanding reader's txnID can be reclaimed. Still thinking about the actual implementation of this, it may make more sense to store the prevTxnID in the freeDB than in each page header. Ideally we want to be able to grab a chunk of pageIDs unambiguously, instead of having to iterate thru each page and read its header to determine if it's safe. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

3 5

RE: slap_timestamp with microsecond granularity?
by Quanah Gibson-Mount 29 Apr '14

29 Apr '14

--On April 29, 2014 at 12:16:59 PM -0700 "Paul B. Henson" <henson(a)acm.org> wrote: > Even more conveniently, it looks like it's getting the microseconds value > from a member of the op structure, the ppolicy_bind_response function in > servers/slapd/overlays/ppolicy.c also has an op structure passed in, which > presumably should have the same microseconds value, so it looks like it > would be very trivial to emulate the above timestamp generating code in > the password policy module. As already noted by Howard, please move this discussion to the openldap-devel list. Thanks! --Quanah -- Quanah Gibson-Mount Server Architect Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

cantor down?
by Quanah Gibson-Mount 24 Apr '14

24 Apr '14

Is cantor down? I can't seem to connect on port 22 or do a git pull of the latest source. Thanks, Quanah -- Quanah Gibson-Mount Server Architect Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Notice to register openldap as maven group name
by Shawn McKinney 09 Apr '14

09 Apr '14

I am planning on changing the namespace used in the openldap fortress projects to org.openldap. In addition to simply changing the packages in source I need to create a new group (org.openldap) in which to publish artifacts to maven central repository. Here's an example of fortress artifacts published to old group, us.joshuatreesoftware: http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22us.joshuatreesoftware%22 Any objections to registering openldap.org as a producer of fortress software artifacts to the maven's central repo? i.e. has someone already done this? Here's more info on topic from sonatype's website: http://central.sonatype.org/pages/producers.html -- 650-963-7681 smckinney(a)symas.com

1 0

really ITS#4365?
by Michael Ströder 02 Apr '14

02 Apr '14

HI! I'm trying to figure out what was recently fixed in RE24. But this comment in CHANGES does not really match the referenced ITS: libldap CR/LF handling (ITS#4365) Maybe I'm overlooking something? Ciao, Michael.

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-devel April 2014