[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: (ITS#8977) Make IDL sizes configurable in back-mdb
--On Friday, February 15, 2019 2:37 PM +0000 hyc@openldap.org wrote:
> Full_Name: Howard Chu
> Version: 2.5
> OS:
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (80.233.42.124)
> Submitted by: hyc
>
>
> IDLs used for index slots are hardcoded to a max of 65536 elements in the
> DB and twice that in memory. Sites with larger DBs tend to need larger
> IDLs; if they're running with sufficient memory it ought to be possible
> to configure larger IDLs.
Per the documentation, this new setting appears to be a new type of
"global" option that affects all MDB databases in the configuration.
This new setting, per the documentation, must be configured in a "backend
mdb" section.
However, there appear to be some problems with the implmentation.
Issue #1: "backend mdb" requires a "directory" directive
Since this is a new "global" concept, "directory" should not be required
(and in fact, seems problematc).
Issue #2: If a "directory" statement is supplied (see above), slapd core
dumps when attempting to convert this configuration to cn=config:
The slapd.conf file I'm using to test is:
include /usr/local/etc/openldap/schema/core.schema
include /usr/local/etc/openldap/schema/cosine.schema
include /usr/local/etc/openldap/schema/inetorgperson.schema
modulepath /usr/local/lib64/openldap
moduleload back_mdb
backend mdb
idlexp 32
database mdb
directory /var/openldap-data
suffix dc=example,dc=com
index default eq
index objectClass
(The directory line location was moved to the "backend" section after
initial testing due to issue #1).
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>