#705 Saving the results of an enumeration takes far too much time
Closed: Fixed Opened by sgallagh.

For an LDAP server of even a moderate number of users (~5000), it can take multiple minutes to save the entries to the LDB cache.

During this save action, all other reads of the LDB are blocked, causing poor responsiveness in the SSSD. We need to perform a careful analysis of how we're saving the data and identify if there are ways that we can make this transaction perform more quickly or at least in a less-blocking manner.

Ticket #658 may aid in this.


An observation: I installed 0.2010120820git583a018.el5 the other day.
Since the update did not go smoothly - the SSSD did not stop, I got stuck and had to clean the mess manually. I enabled the enumeration and it really took several minutes to resolve approximately that amount of entries. I am running debug 9 so I looked at the log. It really spat a lot of debug data there so I thought that performance degradation is related to the level of verbosity however it might not be entirely true.

May be have an option to run scheduled enumerations (once we sort out calendaring)?

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.5.1

Fields changed

coverity: =>
status: new => assigned

Fixed by
- 337d3d9ba9e271272046feac0d17911d024eb43f
- 09c0743a72604dcae32be246326990bc44e01b44

resolution: => fixed
status: assigned => closed
upgrade: => 0

Fields changed

rhbz: => 0

Metadata Update from @sgallagh:
- Issue assigned to sgallagh
- Issue set to the milestone: SSSD 1.5.1

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/1747

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata