Bug 1627846
| Summary: | Contention on virtual attribute lookup | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | German Parente <gparente> |
| Component: | 389-ds-base | Assignee: | thierry bordaz <tbordaz> |
| Status: | CLOSED ERRATA | QA Contact: | RHDS QE <ds-qe-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.7-Alt | CC: | anazmy, cpelland, mreynolds, nkinder, pasik, rmeggins, spichugi, tbordaz, vashirov |
| Target Milestone: | rc | ||
| Target Release: | 7.7 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 389-ds-base-1.3.9.1-4.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: |
Cause: When evaluating a filter component, it is necessary to check if the attribute is real or virtual
Consequence: Contention on a RW lock protecting the list of virtual attributes even if the lock is most often free or acquired in read.
Fix: The search thread acquires the lock in read and set a flag, into a private thread variable, so that further access to the list will just check the flag.
Result: no more contention on virtual attribute lock
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-06 12:58:51 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
German Parente
2018-09-11 16:58:54 UTC
Fix pushed upstream -> POST Build tested: 389-ds-base-1.3.9.1-10.el7.x86_64 Acceptance tests pass, I don't see the stack traces from the description anymore. Marking as VERIFIED, SanityOnly. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2152 |