Bug 1278729
| Summary: | Share nsslapd-threadnumber in the case nunc-stans is enabled, as well. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jan Kurik <jkurik> |
| Component: | 389-ds-base | Assignee: | Noriko Hosoi <nhosoi> |
| Status: | CLOSED ERRATA | QA Contact: | Viktor Ashirov <vashirov> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.0 | CC: | jkurik, mnavrati, msauton, nhosoi, nkinder, rmeggins |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 389-ds-base-1.3.4.0-20.el7_2 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, when nunc-stans was enabled, the default thread number was 3, and the thread number was controlled by the MAX_THREADS environment variable. With this update, the value of the nsslapd-threadnumber configuration parameter is used instead of obtaining the thread number from MAX_THREADS.
|
Story Points: | --- |
| Clone Of: | 1278584 | Environment: | |
| Last Closed: | 2015-12-08 10:33:54 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1278584 | ||
| Bug Blocks: | |||
|
Description
Jan Kurik
2015-11-06 10:02:05 UTC
Build tested: 389-ds-base-1.3.4.0-21.el7_2.x86_64 # tail -n1 /etc/profile export MAX_THREADS=100 nsslapd-threadnumber: 30 nsslapd-enable-nunc-stans: off # ps huH p $(pidof ns-slapd) | wc -l 41 nsslapd-enable-nunc-stans: on # ps huH p $(pidof ns-slapd) | wc -l 72 On the older version (389-ds-base-1.3.4.0-19.el7.x86_64): nsslapd-enable-nunc-stans: off # ps huH p $(pidof ns-slapd) | wc -l 41 nsslapd-enable-nunc-stans: on # ps huH p $(pidof ns-slapd) | wc -l 142 Looks like nunc-stans created additional thread pool (30 + 100 + 12 service threads). And on a new version it's 30 + 30 + 12. So the original issue is fixed, so I mark this bug as VERIFIED. For the mentioned issue new bug will be opened. 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://rhn.redhat.com/errata/RHBA-2015-2572.html |