Bug 485348 - timelimit not honored in some cases
Summary: timelimit not honored in some cases
Alias: None
Product: 389
Classification: Retired
Component: Database - Indexes/Searches
Version: 1.1.3
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Noriko Hosoi
QA Contact: Chandrasekar Kannan
Depends On:
Blocks: 249650 FDS1.2.0
TreeView+ depends on / blocked
Reported: 2009-02-13 00:09 UTC by Noriko Hosoi
Modified: 2015-01-04 23:36 UTC (History)
3 users (show)

Fixed In Version: 8.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-04-29 23:10:29 UTC

Attachments (Terms of Use)
cvs commit message (860 bytes, text/plain)
2009-02-13 00:11 UTC, Noriko Hosoi
no flags Details

Description Noriko Hosoi 2009-02-13 00:09:51 UTC
Description of problem:
Duplicating bz 484157 for RHDS8.1:
484157 -  rhds71 (from rhcs71) timelimit not honored in some cases

Steps to reproduce the problem:
0. import a large ldif file (>= 500K entries)
1. Run ldapsearch with an range search as well as the time limit.  The attribute in the range search filter should be indexed.
ldapsearch -h <host> -p <port> -D "cn=directory manager" -w <pw> -b "<base_dn>" -l <timelimit> "(&(attr>=value_1)(attr<=value_2))"

If the ldapsearch command finishes much longer than <timelimit> (e.g., <timelimit> + 10 seconds) and the return code is 3 (time limit exceeded), the bug is reproduced.

Expected result: the command finishes in (<timelimit> + 2) seconds.

Comment 1 Noriko Hosoi 2009-02-13 00:11:20 UTC
Created attachment 331783 [details]
cvs commit message

Checked in into CVS HEAD.

Comment 2 Yi Zhang 2009-04-08 23:43:12 UTC
by the way, I have 300k entries in DB before i fetch this ldapsearch

[root@mv32a-vm slapd-mv32a-vm]# /usr/lib/mozldap/ldapsearch -D "CN=DIRECTORY MANAGER" -w redhat123 -s sub -b "dc=example,dc=com" -l 1 "uid=*DB*663*" dn
version: 1
dn: uid=DBroca6635, ou=Product Testing, dc=example,dc=com

dn: uid=VLoadbuil9663, ou=Product Development, dc=example,dc=com
ldap_search: Timelimit exceeded

bug verified, closed

Comment 3 Chandrasekar Kannan 2009-04-29 23:10:29 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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