pstack is a gdb wrapper command to dump backtrace of all threads. installing gdb you may get it.
I suspect that the culprit could be the evaluation of the filter over the matching entries (~500 groups owning cn=sampleuser). Using ldapsearch could you reproduce with '-e manageDSAit' option and check if there is still a diff between 1.4.4 and 2.0.
Another investigation is to put a breakpoint on slapi_vattr_filter_test. With such filter it should not be called.
Just for confirmation, you indexed 'uniqueMember' did you indexed in 'eq' ?
Hello Thierry,I can confirm index on 'uniqueMember' for both versions. I also tried to recreate and reindex 'uniqueMember', same result.SRCH-records are inconspicuous, except high optime (no notes..)What exactly do you want to see in pstacks. Do you mean the output from pstack-tool?regardsClaas
_______________________________________________ 389-users mailing list -- firstname.lastname@example.org To unsubscribe send an email to email@example.com 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://firstname.lastname@example.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue