Description of problem: Entry cache and dn cache size are checked by dblayer_is_cachesize_sane which was originally implemented for db cache and it reset the db cache size.
The function not just compairing the given cache size with the available physical memory size, but resetting the size, which is not necessary for the entry cache.
Steps to reproduce the problem:
nsslapd-cachememsize: 8388608 nsslapd-dncachememsize: 8388608
nsslapd-cachememsize: 6710886 nsslapd-dncachememsize: 6710886
nsslapd-cachememsize: 5368708 nsslapd-dncachememsize: 5368708
nsslapd-cachememsize: 4294966 nsslapd-dncachememsize: 4294966
go on and on and on...
git patch file (master) 0001-Ticket-48190-idm-ipa-389-ds-base-entry-cache-converg.patch
Reviewed by Mark (Thank you!!)
Pushed to master: 03d3455..bf9ef71 master -> master commit bf9ef71
Pushed to 389-ds-base-1.3.3: f6fe5bf..a805e25 389-ds-base-1.3.3 -> 389-ds-base-1.3.3 commit a805e25
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.3.3.10
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1521
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.