Project

General

Profile

Actions
Copy link

Bug #6108

closed

Bug #5965: LDAP configuration is not optimized for Rudder use case

Charge data in cache when openldap restart

Added by François ARMAND almost 10 years ago. Updated almost 10 years ago.

Status:
Released
Priority:
3
Assignee:
Matthieu CERDA
Category:
Performance and scalability
Target version:
2.11.7
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

All the optimisation ideas behind #5965 is to have all entries in OpenLDAP cache. If they are not, performances will be horrible.

So each time openldap start, we need to execute the following search:

/var/rudder/ldap/openldap-data# ldapsearch -x -D "cn=Manager,cn=rudder-configuration" -w secret -b cn=rudder-configuration -s sub * + > /dev/null

Perhaps could we handle that in the rudder-slapd start-up script, in a background process ?

Actions
Copy link

Also available in: Atom PDF