Bug 1017418
Summary: | DS performance issues on RHEL65 - frequent hangs doing ldapsearch with ldclt | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Ján Rusnačko <jrusnack> | ||||||||
Component: | 389-ds-base | Assignee: | mreynolds | ||||||||
Status: | CLOSED WORKSFORME | QA Contact: | Sankar Ramalingam <sramling> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 6.5 | CC: | jgalipea, mreynolds, nhosoi, nkinder | ||||||||
Target Milestone: | rc | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2014-04-21 14:57:15 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: | |||||||||||
Bug Depends On: | |||||||||||
Bug Blocks: | 966781, 1061410 | ||||||||||
Attachments: |
|
Description
Ján Rusnačko
2013-10-09 20:29:07 UTC
Created attachment 810164 [details]
Generated stacktrace - DS when hung up
Created attachment 810179 [details]
Stacktrace of ldclt during search
(In reply to Ján Rusnačko from comment #1) > Created attachment 810164 [details] > Generated stacktrace - DS when hung up The server looks idle to me. All the worker threads are not doing any job. (In reply to Ján Rusnačko from comment #0) > Created attachment 810163 [details] > Output of ldclt doing ldapsearch ldclt version 4.23 /usr/bin/ldclt-bin -h ibm-x3650m4-02-vm-02.lab.eng.bos.redhat.com -p 389 -D uid=tuser1,ou=people,dc=example,dc=com -w Secret123 -b ou=people,dc=example,dc=com -f uid=tuser2 -e bindonly -e bindeach -e esearch -n 8 -v -q -I-1 I'm wondering if you need both "bindonly" and "esearch"? Could you try running the command line without "-e bindonly"? (In reply to Noriko Hosoi from comment #6) > (In reply to Ján Rusnačko from comment #0) > > Created attachment 810163 [details] > > Output of ldclt doing ldapsearch > > ldclt version 4.23 > /usr/bin/ldclt-bin -h ibm-x3650m4-02-vm-02.lab.eng.bos.redhat.com -p 389 -D > uid=tuser1,ou=people,dc=example,dc=com -w Secret123 -b > ou=people,dc=example,dc=com -f uid=tuser2 -e bindonly -e bindeach -e esearch > -n 8 -v -q -I-1 > > I'm wondering if you need both "bindonly" and "esearch"? Could you try > running the command line without "-e bindonly"? I see the same behavior without -e bindonly. bindeach and bindonly are more critical to the reproduction of this bug. The bug is that the server becomes so busy processing new LDAP connections that it cannot process incoming LDAPS connections (or LDAPI). The new connection happens with ldap bind. So ideally you would have a client that does nothing but connect/bind/disconnect. That is supposed to be what -e bindonly -e bindeach does. I am still unable to reproduce this behavior. I see some slight temporary dips in performance, but nothing specific with LDAP verses LDAPS. I had a separate client machine issuing non-SSL traffic(tested 1 thread up to 20 threads), then I introduce SSL traffic, and it still runs just fine. Not sure what else I can do on this one. |