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?
Show replies by date