Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/537

Background info:
The ticket #519 "Search with a complex filter including range search is slow" was a complaint against the complex filter that includes open ended range search, e.g., "(modifyTimestamp>=20120101010101Z)".  To reduce the elapsed time, we introduced nsslapd-rangelookthroughlimit not to create an ID list if the range search result gets larger (5000 by default).

Regardless of the complexity of the filter, the range search is slow in general since we merge the ID list containing one ID to the primary ID list every time an entry is found to satisfy the range search filter.  Rather, we should be able to implement an idl range search API that could generate an ID list without merging.

moving all ON_QA bugs to MODIFIED in order to add them to the errata (can't add bugs in the ON_QA state to an errata).  When the errata is created, the bugs should be automatically moved back to ON_QA.

This fix is for performance, so there is no clear behavioural difference.

You could run a sanity check on the range search to verify nsslapd-rangelookthroughlimit is properly evaluated.

[root@dhcp201-149 ~]# cat /etc/dirsrv/slapd-dhcp201-149/dse.ldif | grep -i "nsslapd-rangelookthroughlimit" 
nsslapd-rangelookthroughlimit: 5000

dbgen.pl -o /export/test.ldif -n 10000

ldif2db.pl -n userRoot -Z dhcp201-149 -D "cn=Directory Manager" -w Secret123 -i /export/test.ldif

ldapsearch -x -h localhost -D "cn=Directory Manager" -w Secret123 -p 389 -b "dc=example,dc=com" "(modifyTimestamp>=20120101010101Z)"

Marking the bug as VERIFIED Sanity Only.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.