Bug 692599
Summary: | 389 DS deadlocks when mass-adding users from multiple processes | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Stephen Gallagher <sgallagh> |
Component: | 389-ds-base | Assignee: | Rich Megginson <rmeggins> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | edewata, nalin, nhosoi, nkinder, rmeggins |
Target Milestone: | --- | Keywords: | screened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: |
Virtual Machine (8 CPUs) running
Fedora 14 i686
|
|
Last Closed: | 2011-04-12 01:04:23 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: |
Description
Stephen Gallagher
2011-03-31 16:40:39 UTC
Stephen - Is this the same issue as bug #692690? Yes, I believe it is. *** This bug has been marked as a duplicate of bug 692690 *** Are you sure? Bug #692690 isn't a deadlock so much as a a-server-thread's-really-busy-right-now which happens to last a long time. Well, I suppose it could be considered a separate issue that slapi-nis taking forever in one thread is causing all other threads to block would be a separate issue. So yeah, I guess we should reopen this. (In reply to comment #4) > Well, I suppose it could be considered a separate issue that slapi-nis taking > forever in one thread is causing all other threads to block would be a separate > issue. > > So yeah, I guess we should reopen this. Does it cause all operations to block? (In reply to comment #5) > (In reply to comment #4) > > Well, I suppose it could be considered a separate issue that slapi-nis taking > > forever in one thread is causing all other threads to block would be a separate > > issue. > > > > So yeah, I guess we should reopen this. > > Does it cause all operations to block? Yes. Once I was in the state described by bug 692690 I could not perform any search, modify, etc. |