Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 953165
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
Steps to Reproduce: 1. Enable enumeration in sssd ldap domain with a significant amount of accounts 2. Fire off a `getent passwd` or something that hits nss and causes enumeration 2. Watch CPU spike to 100% Actual results: CPU spikes to 100% Expected results: CPU usage ~2% Additional info: Are we seeing some sort of regression? Looks like this amount of CPU usage is excessive when compared to previous versions of sssd.
Lukas was triaging the bug and traced the regression down to commit e4fb78b
Fields changed
blockedby: => blocking: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => priority: major => blocker review: True => 0 selected: => testsupdated: => 0
milestone: NEEDS_TRIAGE => SSSD 1.10 beta
owner: somebody => jhrozek status: new => assigned
patch: 0 => 1
resolution: => fixed status: assigned => closed
We'll need to release this fix in the maintenance branch, too. Moving to 1.9.6
milestone: SSSD 1.10 beta => SSSD 1.9.6
changelog: => Due to a logic bug in the LDAP provider, the SSSD was performing an unnecessary search when saving enumerated entries. This could have caused a CPU spike in large environments.
Metadata Update from @jhrozek: - Issue assigned to jhrozek - Issue set to the milestone: SSSD 1.9.6
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/2935
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.
Login to comment on this ticket.