Bug 132801 - openldap cannot handle modify during large searches
Summary: openldap cannot handle modify during large searches
Keywords:
Status: CLOSED DUPLICATE of bug 132800
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: openldap
Version: 3.0
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Jay Turner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-09-17 07:51 UTC by Håkan Wessberg
Modified: 2015-01-08 00:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:05:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Håkan Wessberg 2004-09-17 07:51:19 UTC
Description of problem:
We have 80.000 entries in a ldbm backend database and cant make
search and modify concurrently. This causes serious problems when
large reads are made that take aprox 4-5 min. During those reads we
cant make any writes and the client that tries to do so hangs until
the read is finished.


Version-Release number of selected component (if applicable):
openldap-2.0.27-17

How reproducible:
Always

Steps to Reproduce:
1. search for a large group of objects.
2. try to modify one object (not necessarily one in the group returned
by the search)
3.
    

Actual Results:  the modify is not performed until all objects is
returned from the search-operation.

Expected Results:  both search and modify should happen conccurently.

Additional info:

Kurt Zeilenga, of openldap fame, responded with when this report was
posted to the openldap-bugs list:
"Trying upgrading.  2.0, as well as 2.1, are considered Historic."

When is RH ready to offer a recent version of openldap?

Comment 1 Håkan Wessberg 2004-09-17 07:52:21 UTC

*** This bug has been marked as a duplicate of 132800 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:05:41 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.