HI!
This is an important note to those who run OpenLDAP slapd based on openSUSE or SLE packages, especially Tumbleweed:
If you're still using OpenLDAP 2.4 or earlier with back-bdb or back-hdb then migrate to back-mdb now because OpenLDAP 2.5 packages won't support these backends anymore!
Disclaimer:
I'm writing as a package maintainer who only updates package "openldap2" in openSUSE Factory/Tumbleweed. I have no official role in openSUSE project nor SUSE.
Background:
As you might already know OpenLDAP 2.5 builds by default have no more support for backends back-hdb and back-bdb based on Berkeley-DB. Furthermore using Berkeley-DB in general is deprecated.
I've received a request to update the openSUSE package "openldap2" and its sub-packages to OpenLDAP release 2.5.7 also removing back-bdb and back-hdb [1]. I'd love to accept this update request really soon because I also want to have the new features in libldap. So the update will hit openSUSE Tumbleweed really soon.
While this change will *not* affect your deployments based on packages from SLE or openSUSE Leap 15.3 or earlier you should prepare your installation for possible future updates by migrating to back-mdb now.
And always use slapcat to backup your database(s) and practice restoring your databases to be prepared for any desaster.
Ciao, Michael.
Hi!
Honestly I'm quite afraid of the "space explosion" that seems to be an inherent feature of MDB. 8-( (Maybe that's just because of my bad experience with earlier BtrFS filesystem (that seems to use similar concepts IMHO))
Regards, Ulrich
Michael Ströder michael@stroeder.com schrieb am 25.08.2021 um 13:43 in
Nachricht 62996401-b45d-898d-3b6b-eab38b80ad44@stroeder.com:
HI!
This is an important note to those who run OpenLDAP slapd based on openSUSE or SLE packages, especially Tumbleweed:
If you're still using OpenLDAP 2.4 or earlier with back-bdb or back-hdb then migrate to back-mdb now because OpenLDAP 2.5 packages won't support these backends anymore!
Disclaimer:
I'm writing as a package maintainer who only updates package "openldap2" in openSUSE Factory/Tumbleweed. I have no official role in openSUSE project nor SUSE.
Background:
As you might already know OpenLDAP 2.5 builds by default have no more support for backends back-hdb and back-bdb based on Berkeley-DB. Furthermore using Berkeley-DB in general is deprecated.
I've received a request to update the openSUSE package "openldap2" and its sub-packages to OpenLDAP release 2.5.7 also removing back-bdb and back-hdb [1]. I'd love to accept this update request really soon because I also want to have the new features in libldap. So the update will hit openSUSE Tumbleweed really soon.
While this change will *not* affect your deployments based on packages from SLE or openSUSE Leap 15.3 or earlier you should prepare your installation for possible future updates by migrating to back-mdb now.
And always use slapcat to backup your database(s) and practice restoring your databases to be prepared for any desaster.
Ciao, Michael.
On 8/26/21 9:41 AM, Ulrich Windl wrote:
Honestly I'm quite afraid of the "space explosion" that seems to be an inherent feature of MDB. 8-(
It's hard to tell about which problem you're talking without the usual technical details: - OS version - OpenLDAP version - which packages you're using - detailed example data
In my personal experience in customer projects migrating to back-mdb is a no-brainer.
Just do it now.
Ciao, Michael.
Michael Ströder michael@stroeder.com schrieb am 25.08.2021 um 13:43 in
Nachricht 62996401-b45d-898d-3b6b-eab38b80ad44@stroeder.com:
HI!
This is an important note to those who run OpenLDAP slapd based on openSUSE or SLE packages, especially Tumbleweed:
If you're still using OpenLDAP 2.4 or earlier with back-bdb or back-hdb then migrate to back-mdb now because OpenLDAP 2.5 packages won't support these backends anymore!
Disclaimer:
I'm writing as a package maintainer who only updates package "openldap2" in openSUSE Factory/Tumbleweed. I have no official role in openSUSE project nor SUSE.
Background:
As you might already know OpenLDAP 2.5 builds by default have no more support for backends back-hdb and back-bdb based on Berkeley-DB. Furthermore using Berkeley-DB in general is deprecated.
I've received a request to update the openSUSE package "openldap2" and its sub-packages to OpenLDAP release 2.5.7 also removing back-bdb and back-hdb [1]. I'd love to accept this update request really soon because I also want to have the new features in libldap. So the update will hit openSUSE Tumbleweed really soon.
While this change will *not* affect your deployments based on packages from SLE or openSUSE Leap 15.3 or earlier you should prepare your installation for possible future updates by migrating to back-mdb now.
And always use slapcat to backup your database(s) and practice restoring your databases to be prepared for any desaster.
Ciao, Michael.
--On Thursday, August 26, 2021 10:49 AM +0200 Michael Ströder michael@stroeder.com wrote:
On 8/26/21 9:41 AM, Ulrich Windl wrote:
Honestly I'm quite afraid of the "space explosion" that seems to be an inherent feature of MDB. 8-(
It's hard to tell about which problem you're talking without the usual technical details:
- OS version
- OpenLDAP version
- which packages you're using
- detailed example data
In my personal experience in customer projects migrating to back-mdb is a no-brainer.
Just do it now.
back-mdb databases are literally smaller than the same back-bdb/hdb db, so I've no clue what is being refernced here either. It is true in some early releases of back-mdb there were some issues with fragmentation but that's been dealt with.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
Quanah Gibson-Mount quanah@symas.com schrieb am 26.08.2021 um 18:26 in
Nachricht <CD9D8026D99CD87ED78D93EE@[192.168.1.28]>:
--On Thursday, August 26, 2021 10:49 AM +0200 Michael Ströder michael@stroeder.com wrote:
On 8/26/21 9:41 AM, Ulrich Windl wrote:
Honestly I'm quite afraid of the "space explosion" that seems to be an inherent feature of MDB. 8-(
It's hard to tell about which problem you're talking without the usual technical details:
- OS version
- OpenLDAP version
- which packages you're using
- detailed example data
In my personal experience in customer projects migrating to back-mdb is a no-brainer.
Just do it now.
back-mdb databases are literally smaller than the same back-bdb/hdb db, so I've no clue what is being refernced here either. It is true in some early
releases of back-mdb there were some issues with fragmentation but that's been dealt with.
Hi Quanah!
So are you saying with repeated modify operations MDB does no longer grow and grow? I got the impression that is does and you'll have to reorganize (export/imort) the database periodically to keep the size in bounds.
Regards, Ulrich
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
--On Friday, August 27, 2021 10:19 AM +0200 Ulrich Windl Ulrich.Windl@rz.uni-regensburg.de wrote:
Hi Quanah!
So are you saying with repeated modify operations MDB does no longer grow and grow? I got the impression that is does and you'll have to reorganize (export/imort) the database periodically to keep the size in bounds.
Generally no. For multivalued attributes that have hundreds or thousands of attribute:value pairs, it was possible for it to be problematic in OpenLDAP 2.4 in certain scenarios. This has been mitigated in OpenLDAP 2.5 with the multival keyword. Most sites do not encounter this issue however.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
openldap-technical@openldap.org
-
Michael Ströder -
Quanah Gibson-Mount -
Ulrich Windl