Comment 36 for bug 16317

Revision history for this message
Debian Bug Importer (debzilla) wrote :

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
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D190165
>=20
> And look at the pile of bugs indicating slapd lockups when using BDB:
> http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=3Dslapd

*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
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCjwHqdQgHtVUb5EcRAgavAJ4nfl5pq2gg2LomJz2JLb9PU1gG2QCbBS9G
sL7m7AGW2UGVRDQoURf29Y4=
=yqzi
-----END PGP SIGNATURE-----

--rS8CxjVDS/+yyDmU--