Uploaded image for project: 'OpenDJ'
  1. OpenDJ
  2. OPENDJ-4367

CURSOR_ENTRY_LIMIT should be configurable

    Details

    • Type: Improvement
    • Status: Done
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.5.0, 4.0.0
    • Fix Version/s: 6.0.0
    • Component/s: common-repo
    • Labels:
    • Support Ticket IDs:

      Description

      Currently CURSOR_ENTRY_LIMIT is hardcoded to 100000:

      opendj-server-legacy/src/main/java/org/opends/server/backends/pluggable/IndexFilter.java:

      /** Limit on the number of entry IDs that may be retrieved by cursoring through an index. */
      static final int CURSOR_ENTRY_LIMIT = 100000;
      

       
      This effectively limits the number of indexed entries that can be searched and sorted. This can be a problem when a server is utilised as CTS for OpenAM and the token reaper search (where coreTokenExpirationDate is less than the current date) returns >100k entries. 

      Whilst the hard coded limit is likely there to protect server resources, it is critical that expired tokens can be deleted efficiently.

      Expectation:
      CURSOR_ENTRY_LIMIT should be a configurable parameter, ideally on a per-user basis. This parameter should only be changed under guidance and the potential risks understood. Probably best implemented as a hidden property.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                joseph.de-menditte Joseph de-Menditte
                Reporter:
                john.noble John Noble
                QA Assignee:
                Viktor Nawrath [X] (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: