On Sat, May 21, 2005 at 04:58:13PM +1200, Martin Langhoff (CatalystIT) wrot=
e:
> As recently as November 2004, I was seeing serious lockups and dataloss=
=20
> with BDB backends, due to upstream bugs in the BDB integration, and all=
=20
> our LDAP setups ended up using LDBM due to reliability concerns.
> Yes, these are old bugs, but they are still open. Is there any=20
> indication from upstream that the problem is fixed?
As I am not running real production systems I have never seen these
lockups. (I used to but that system is still running woody with an aged
version of OpenLDAP and I am no longer responsible). Therefore I can't
really acknowledge that. Given the number of yields in the code which
seem to work around locking problems I don't have a good feeling...
> Now, with LDBM broken as well, I am not sure what to do, really.=20
> Switching to BDB is really risky -- I haven't seen the it work reliably=
=20
> at all. It has been severely broken in every version I tried in the=20
> 2.0.x and 2.2.x series of OpenLDAP, both from OpenLDAP and from the=20
> corresponding Debian packages.
=20
As Stanford is using it I'd expect it to be reliable enough for
production use. So going to BDB is probably the best bet.=20
Greetings
Torsten
--rS8CxjVDS/+yyDmU
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
Message-ID: <email address hidden>
Date: Sat, 21 May 2005 11:39:54 +0200
From: Torsten Landschoff <email address hidden>
To: "Martin Langhoff (CatalystIT)" <email address hidden>,
<email address hidden>
Subject: Re: Bug#304735: How stable is BDB?
--rS8CxjVDS/+yyDmU Disposition: inline Transfer- Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Content-
Content-
On Sat, May 21, 2005 at 04:58:13PM +1200, Martin Langhoff (CatalystIT) wrot=
e:
> As recently as November 2004, I was seeing serious lockups and dataloss=
=20
> with BDB backends, due to upstream bugs in the BDB integration, and all=
=20
> our LDAP setups ended up using LDBM due to reliability concerns.
Understandably.
> These BDB reliability concerns are tracked in Bug #190165=20 bugs.debian. org/cgi- bin/bugreport. cgi?bug= 3D190165 bugs.debian. org/cgi- bin/pkgreport. cgi?pkg= 3Dslapd
> http://
>=20
> And look at the pile of bugs indicating slapd lockups when using BDB:
> http://
*sigh* Yes.
> Yes, these are old bugs, but they are still open. Is there any=20
> indication from upstream that the problem is fixed?
As I am not running real production systems I have never seen these
lockups. (I used to but that system is still running woody with an aged
version of OpenLDAP and I am no longer responsible). Therefore I can't
really acknowledge that. Given the number of yields in the code which
seem to work around locking problems I don't have a good feeling...
> Now, with LDBM broken as well, I am not sure what to do, really.=20
> Switching to BDB is really risky -- I haven't seen the it work reliably=
=20
> at all. It has been severely broken in every version I tried in the=20
> 2.0.x and 2.2.x series of OpenLDAP, both from OpenLDAP and from the=20
> corresponding Debian packages.
=20
As Stanford is using it I'd expect it to be reliable enough for
production use. So going to BDB is probably the best bet.=20
Greetings
Torsten
--rS8CxjVDS/+yyDmU pgp-signature; name="signature .asc" Description: Digital signature Disposition: inline
Content-Type: application/
Content-
Content-
-----BEGIN PGP SIGNATURE-----
HtVUb5EcRAgavAJ 4nfl5pq2gg2LomJ z2JLb9PU1gG2QCb BS9G oURf29Y4=
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFCjwHqdQg
sL7m7AGW2UGVRDQ
=yqzi
-----END PGP SIGNATURE-----
--rS8CxjVDS/ +yyDmU- -