Bug 56112 - Group membership cache always reads LDAP from primary server
Group membership cache always reads LDAP from primary server
Status: NEW
Product: UCS
Classification: Unclassified
Component: LDAP
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2023-06-02 10:51 CEST by Julia Bremer
Modified: 2023-06-09 15:30 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?: Yes
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2023052621000404
Bug group (optional): Large environments, UCS Performance
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Julia Bremer univentionstaff 2023-06-02 10:51:29 CEST
The univention-group-membership cache has been created to improve performance 
and has been integrated into the portal. 

Since the univention-ldap-cache uses getMachineConnection to read from LDAP, it uses the primary server as default, which is not needed for the cache, as it is read only. 

This can result in very high load for the slapd on the primary server as discovered on customer systems.