It's a percentage of the available memory to use for the caches, not "enabled/disabled".Thank you Mark !
why : nsslapd-cache-autosize: 25 and not set the value to = 1 -enabld ?
From: Mark Reynolds <mareynol@redhat.com>
Sent: Wednesday, February 4, 2026 11:56:12 AM
To: General discussion list for the 389 Directory server project.
Cc: Ghiurea, Isabella
Subject: [EXTERNAL\EXTERNE:] Re: [389-users] missing nssalpd-cachec-autosizing in 3.1.3***Attention*** This email originated from outside of the NRC. ***Attention*** Ce courriel provient de l'extérieur du CNRC.
There are many configuration settings that are not written in the dse.ldif unless their default value is changed. Instead please use the CLI tools to manage the configuration:
# dsconf slapd-localhost backend config get
nsslapd-lookthroughlimit: 5000
nsslapd-mode: 600
nsslapd-idlistscanlimit: 2147483646
nsslapd-systemidlistscanlimit: 5000
nsslapd-directory: /var/lib/dirsrv/slapd-localhost/db
nsslapd-import-cachesize: 16777216
nsslapd-idl-switch: new
nsslapd-search-bypass-filter-test: on
nsslapd-search-use-vlv-index: on
nsslapd-exclude-from-export: entrydn entryid dncomp parentid numSubordinates tombstonenumsubordinates entryusn
nsslapd-serial-lock: on
nsslapd-pagedlookthroughlimit: 0
nsslapd-pagedidlistscanlimit: 0
nsslapd-rangelookthroughlimit: 5000
nsslapd-backend-opt-level: 1
nsslapd-backend-implement: mdb
nsslapd-db-durable-transaction:
nsslapd-dynamic-lists-enabled: off
nsslapd-dynamic-lists-attr: member
nsslapd-dynamic-lists-oc: groupOfUrls
nsslapd-dynamic-lists-url-attr: memberURL
nsslapd-mdb-max-size: 21474836480
nsslapd-mdb-max-readers: 0
nsslapd-mdb-max-dbs: 512
nsslapd-cache-autosize: 25
# dsconf slapd-localhost backend suffix get dc=example,dc=com
dn: cn=userroot,cn=ldbm database,cn=plugins,cn=config
nsslapd-cachememsize: 15099494400
nsslapd-cachesize: -1
nsslapd-dncachememsize: 1677721600
nsslapd-readonly: off
nsslapd-require-index: off
nsslapd-state: backend
nsslapd-suffix: dc=example,dc=com
On 2/4/26 1:48 PM, Ghiurea, Isabella via 389-users wrote:
HI 389-DS List.
I am testing the following DS installation 389-ds-base-libs-3.1.3 , the RH Docs mentioned for tuning the DS there is a an important parameter: nsslapd-cache-autosize in 3.1 version , but I am not seeing this entry in dse.ldif .
I cfg the DS instance for ' mdb' database in template file >> this should be the mem db not the Berkley db .({ there are still entries in dse.ldif related to Berkely db I understood this db is obsolete now )}
Which one of the following parameters is related to cache_autosize?
This is from dse.ldif
nsslapd-cachesize: -1
nsslapd-cachememsize: 512000
^^^ These are the entry cache settings and they are independent of the underlying database library. The cache autosizing should override these values. You can verify what it uses in the errors log when the server starts up.
In BDB there were "dbcache settings" but this concept does not exist in mdb so those settings are no longer present. There are no "obsolete" bdb settings in the config anymore so I think there is a misunderstanding about whatever settings you are referring to.
Anyway, please use "dsconf" to view/edit the configuration.
HTH,
Mark
nsslapd-readonly: off
nsslapd-require-index: off
nsslapd-require-internalop-index: off
nsslapd-dncachememsize: 16777216
numSubordinates: 4
And more default cfg
nsslapd-lookthroughlimit: 5000
nsslapd-mode: 600
nsslapd-idlistscanlimit: 2147483646
nsslapd-directory: /var/lib/dirsrv/slapd-testldap/db
nsslapd-import-cachesize: 16777216
nsslapd-idl-switch: new
nsslapd-search-bypass-filter-test: on
nsslapd-search-use-vlv-index: on
nsslapd-exclude-from-export: entrydn entryid dncomp parentid numSubordinates tombstonenumsubordinates entryusn
nsslapd-serial-lock: on
nsslapd-pagedlookthroughlimit: 0
nsslapd-pagedidlistscanlimit: 0
nsslapd-rangelookthroughlimit: 5000
nsslapd-backend-opt-level: 1
nsslapd-backend-implement: mdb
nsslapd-db-durable-transaction:
nsslapd-mdb-max-size: 7408818586
nsslapd-mdb-max-readers: 0
nsslapd-mdb-max-dbs: 512
Thank you for your feedback!
-- Identity Management Development Team
-- Identity Management Development Team
No comments:
Post a Comment