#8962 Info about searchrecordslimit set search limit to 10,000 after upgrade
Closed: fixed by frenaud. Opened by rcritten.

Ticket was cloned from Red Hat Bugzilla: Bug 1966289

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

The jist is there is confusion because there are several search limits, with the default limit in 389-ds being 2000.

User tried ipa config-mod --searchrecordslimit=10000 and that didn't do what they expected.

There was an attempt years ago to set the default at 100k but due to an issue with the way the update entry was created it is a no-op.

Flo describes it well that ipa config-mod updates the client side search limit only and not any server side sizing.


Metadata Update from @rcritten:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1966289

Metadata Update from @rcritten:
- Issue assigned to rcritten

https://github.com/freeipa/freeipa/pull/5985

master:

  • b91c0afd0b5ae9eb4954078f8c76f2914daa1d85 Increase default limit on LDAP searches to 100k

ipa-4-9:

  • 3fb0f5333613beabeead3feb73dc0fea9694bcdc Increase default limit on LDAP searches to 100k

Metadata Update from @frenaud:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

Metadata Update from @rcritten:
- Custom field changelog adjusted to Set the server-side search size limit to 10,000 entries. By default the client side will still be 100. Consider carefully when increasing the client side value as it adds additional load on the server to retrieve more entries.

master:

  • 56e4f33ce630a6a310518f25b67d46fb31f7919e ipatests: Test default value of nsslapd-sizelimit.

ipa-4-9:

  • 465f1669a6c5abc72da1ecaf9aefa8488f80806c ipatests: Test default value of nsslapd-sizelimit.
Metadata