We are running a 389 Directory Server as our Identity Store Backend for years. Recently I saw the number of unindexed searches inreased and CPU consumption doubled. After some investigation I found that the number of entries with a certain objectClass (with a certain base DN) became higher than 4000 causing that unwanted behaviour. After some further investigation I saw that other object classes (eg. groups and org-units) have numbers between 6000 and 10000. Searches on these objectClasses also show 'notes=A'. So I tend to change the value of nsslapd-idlistscanlimit to 12000. Your Opinion?
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
No comments:
Post a Comment