Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-6483

Segment-based composite node store performance degradation

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Won't Fix
    • 1.7.4
    • 1.7.9, 1.8.0
    • composite
    • None

    Description

      It seems that the OAK-4732 is not compatible with the composite node store using a segment node store as the main (writeable) store. The OAK-4732 measures how much does it usually take to apply commit hooks and merge the new root. However, the composite node store plugs into the commit hook and reads other node store states. As a result, it may take quite a while and the measured values are big. They are then used to tune the lock inside the LockBasedScheduler#getHeadNodeState() method. Since the times are big, the method also waits a long time for the semaphore before it gives up. This causes performance degradation.

      The -Doak.scheduler.fetch.commitDelayQuantile=0 parameter can be used to disable the OAK-4732.

      Attachments

        Issue Links

          Activity

            People

              tomek.rekawek Tomek Rękawek
              tomek.rekawek Tomek Rękawek
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: