From 5199cdb5b7b3535d483c92aa9b1f1aa7c5418364 Mon Sep 17 00:00:00 2001 From: Quanah Gibson-Mount Date: Fri, 30 Jan 2009 19:44:19 +0000 Subject: [PATCH] ITS#5721 --- CHANGES | 1 + doc/man/man5/slapd-bdb.5 | 6 ++++++ 2 files changed, 7 insertions(+) diff --git a/CHANGES b/CHANGES index be9d2728e8..01eadf5ff2 100644 --- a/CHANGES +++ b/CHANGES @@ -54,6 +54,7 @@ OpenLDAP 2.4.14 Engineering Fixed uuid_create/uuid_unparse_lower detection (ITS#5905) Documentation admin24 added limits chapter (ITS#5818) + slapd-bdb/hdb expansion on dncachesize behavior (ITS#5721) slapo-constraint(5) example fix (ITS#5895) OpenLDAP 2.4.13 Release (2008/11/24) diff --git a/doc/man/man5/slapd-bdb.5 b/doc/man/man5/slapd-bdb.5 index 68a9f22b6d..677747f0dc 100644 --- a/doc/man/man5/slapd-bdb.5 +++ b/doc/man/man5/slapd-bdb.5 @@ -148,6 +148,12 @@ will return a different result. Specify the maximum number of DNs in the in-memory DN cache. The default is twice the \fBcachesize\fP. Ideally this cache should be large enough to contain the DNs of every entry in the database. +It should be noted that the \fBDN cache\fP is allowed to temporarily +grow beyond the configured size. It does this if many entries are +locked when it tries to do a purge, because that means they're +legitimately in use. Also, the \fBDN cache\fP never purges entries +that have cached children, so depending on the shape of the DIT, it +could have lots of cached DNs over the defined limit. .TP .BI idlcachesize \ Specify the size of the in-memory index cache, in index slots. The -- 2.39.5