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

Online rebuild-index memory calculation is inappropriate when multiple PDB backends are involved

    Details

    • Support Ticket IDs:
    • Story Points:
      0

      Description

      To reproduce:

      1) Setup standalone DJ with 2GB heap and 4 PDB backends of 10% db-cache, on a server with 8 CPUs. Have some entries in at least one of the backends.
      2) Run online rebuild index

      Result:

      Server should run out of memory

      Expected result:

      The above configuration (40%/2GB/8CPUS) seems like a very reasonable configuration and should not lead to memory problems.

      Depending on other parameters this can be reproduced even more easily, for example if there are more CPUs/worker threads or a few more indexes on the backends etc.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ian.packer Ian Packer [X] (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: