[389-users] Search results with memberOf plugin is very slow
We’re new to LDAP within the last year as we’re replacing our RDBMS of users with a
directory server. We’re running Scientific Linux 6 with (stable) version 1.2.11. My
apologies if this has been asked before.
Has anyone else noticed very slow searching with 389 ds? Especially with a large list of
results. It seems as though the memberOf plugin is getting in the way with the amount of
checking its doing combined with some threading issues. In one case, during load testing,
we were able to make the thread hang and were able to see the thread contents as such:
….
#14 0x00007f4c028dc04b in memberof_call_foreach_dn () from
/usr/lib64/dirsrv/plugins/libmemberof-plugin.so
#15 0x00007f4c028dc4bd in memberof_get_groups_callback () from
/usr/lib64/dirsrv/plugins/libmemberof-plugin.so
#16 0x00007f4c0c785a8f in send_ldap_search_entry_ext () from
/usr/lib64/dirsrv/libslapd.so.0
#17 0x00007f4c0c7867fc in send_ldap_search_entry () from /usr/lib64/dirsrv/libslapd.so.0
#18 0x00007f4c0c7694a6 in iterate.clone.2 () from /usr/lib64/dirsrv/libslapd.so.0
#19 0x00007f4c0c769957 in send_results_ext.clone.0 () from
/usr/lib64/dirsrv/libslapd.so.0
#20 0x00007f4c0c76a6ad in op_shared_search () from /usr/lib64/dirsrv/libslapd.so.0
#21 0x00007f4c0c776c2c in search_internal_callback_pb () from
/usr/lib64/dirsrv/libslapd.so.0
#22 0x00007f4c028dc04b in memberof_call_foreach_dn () from
/usr/lib64/dirsrv/plugins/libmemberof-plugin.so
#23 0x00007f4c028dc1a2 in memberof_fix_memberof_callback () from
/usr/lib64/dirsrv/plugins/libmemberof-plugin.so
#24 0x00007f4c028dcd40 in memberof_modop_one_replace_r () from
/usr/lib64/dirsrv/plugins/libmemberof-plugin.so
#25 0x00007f4c028de10f in memberof_replace_list () from
/usr/lib64/dirsrv/plugins/libmemberof-plugin.so
#26 0x00007f4c028de576 in memberof_postop_modify () from
/usr/lib64/dirsrv/plugins/libmemberof-plugin.so
….
We maintain a tree of Users and a tree of Groups, with the memberOf plugin identifying,
for each user, each group they are a member of via the memberOf attribute. Seems like a
fairly typical setup.
I’m trying to convince our Administrator to upgrade to the latest (1.3.4.4 as of this
writing), but I can’t find a change log to refer to incase this has been fixed already.
Many thanks,
Dustin