#885 Investigate and determine the best approach for SSSD winbind back end
Closed: Fixed None Opened 12 years ago by dpal.

There are two approaches: use constrained threads or prefork a pool of processes. A discussion should be held to determine the best approach. If we go with threads we should consider using same approach in the proxy back end. A ticket should be filed to do the work.


We had a discussion on this at last week's status meeting.

The general consensus was that we would prefer a prefork pool rather than threads, as there is some concern about the thread-safety of libtevent. Also, the coding standard up to this point has been to prefer processes, so we'd rather keep consistent.

type: defect => task

Have you considered something like Apache's prefork model for the process pool management?

They seem to simply create a new process into the pool whenever the number of idle processes is lower than min_spare_processes and kill then off when they have more than max_spare_processes. Also they have hard limits in the form of min_processes and max_processes.

Fields changed

milestone: SSSD 1.6.0 => SSSD 1.8.0

Updated with diagrams and more description as requested: https://fedorahosted.org/sssd/wiki/DesignDocs/AsyncWinBind

rhbz: =>

Fields changed

milestone: SSSD 1.8.0 => NEEDS_TRIAGE

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.8 AD Integration NEEDS TRIAGE

Fields changed

resolution: => fixed
status: new => closed

Fields changed

rhbz: => 0

Metadata Update from @dpal:
- Issue assigned to pzuna
- Issue set to the milestone: SSSD 1.8 AD Integration NEEDS TRIAGE

7 years ago

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

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.

Login to comment on this ticket.

Metadata