Performance issue when deleting a user being part of very large groups (40K users): user-del lasts up to 6 min
The performance hit is due to DS during the LDAP DEL of the user. Several internal LDAP requests (during LDAP DEL) participated to the overall duration but by far (99%) the most expensive is triggered by referential integrity plugin that deletes the deleted user from the groups it was memberof. More specifically the expensive part is when building a sorted array of the deleted members (a_deleted_values) of the group
freeipa 4.4 DS 1.3.5
Test case would be: - install freeipa - install master and a replica (This is important to be in a replicated topology so that urp keeps deleted values). - Provision 20000 users (better to user https://github.com/freeipa/freeipa-tools/blob/master/create-test-data.py) - Delete a given user
user-del last several minutes
user-del should be much more rapid, like few seconds
Metadata Update from @tbordaz: - Custom field type adjusted to defect
Metadata Update from @tbordaz: - Custom field origin adjusted to IPA
Metadata Update from @tbordaz: - Issue assigned to tbordaz
In my tests the first removed users are fast. After 4 hours approximately running the task, the bad performance is observed.
N >= 13 000 users
If I cancel the task and wait for a few days, the IPA returns to normal process. Even if I restart the IPA and server, the problem persists several days.
Actually it was a known bug https://fedorahosted.org/389/ticket/48894. That was already fixed 1.3.6.1-2.
Would you try this version ?
Metadata Update from @tbordaz: - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
Hello, this version is not available in CentOS 7.3. The current version is 1.3.5.10-18. It is good to know that it has already been resolved.
Thanks.
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/2345
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: duplicate)
Log in to comment on this ticket.