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

Over allocation of db-cache-percent for existing backend results in empty error

    Details

    • Story Points:
      0
    • Support Ticket IDs:

      Description

      Steps to reproduce:

       

      1. Create a second backend to bring total db-cache-percent to 100%

      2. Increase db-cache-percent for any backend to bring the total to >100%, i.e.

       

      ./dsconfig set-backend-prop --port 4444 -D "cn=Directory Manager" --bindPassword password --backend-name backend2 --set db-cache-percent:30 --trustAll --no-prompt
      
      The JE Backend could not be modified because of the following reason:
      
      * Unwilling to Perform: Entry
       ds-cfg-backend-id=backend3,cn=Backends,cn=config cannot be modified
       because one of the configuration change listeners registered for that
       entry rejected the change:
      

       

      If a new backend is created with an over-allocated  db-cache-percent, you get a nice descriptive error, i.e.

      The JE Backend could not be created because of the following reason:
      
      * Unwilling to Perform: The Directory Server is unwilling to add
       configuration entry ds-cfg-backend-id=backend3,cn=Backends,cn=config
       because one of the add listeners registered with the parent entry
       cn=Backends,cn=config rejected this change with the message:
       Configuration attribute ds-cfg-db-cache-percent has a value of 50% but
       the JVM has only 10% available
      

       

      Expectation:

      Over-allocating the  db-cache-percent for existing backends should give a descriptive error similar to when a new backend is created

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                matthew Matthew Swift
                Reporter:
                john.noble John Noble
                Dev Assignee:
                Matthew Swift
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: