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

leaseUpdateThread might be blocked by leaseUpdateCheck

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments


    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.4, 1.5.14
    • Fix Version/s: 1.4.15, 1.6.0
    • Component/s: core
    • Labels:


      cloned from OAK-5446 due to internal JIRA issues

      Fighting with cluster nodes losing their lease and shutting down oak-core in a cloud environment. For reasons unknown at this point in time, the whole process seems to skip about two minutes of real time.

      This is a situation from which oak currently does not recover. Code analysis shows that ClusterNodeInfo is handed the LeaseCheckDocumentStoreWrapper instance to use as store. This is fatal since any action the renewLease() tries to do will first invoke the performLeaseCheck(). The lease check will, when the FailureMargin is reached, stall the renewLease() thread for 5 retry attempts and then declare the lease to be lost.

      The ClusterNodeInfo should instead be using the "real" DocumentStore, not the wrapped one, IMO.


        1. [#OAK-5446] leaseUpdateThread might be blocked by leaseUpdateCheck.html
          39 kB
          Julian Reschke
        2. OAK-5446.diff
          4 kB
          Julian Reschke
        3. OAK-5446.testcase
          4 kB
          Julian Reschke
        4. OAK-5446.testcase.v3
          5 kB
          Julian Reschke
        5. OAK-5446.xml
          25 kB
          Julian Reschke
        6. OAK-5446-jr.diff
          5 kB
          Julian Reschke

        Issue Links



            • Assignee:
              reschke Julian Reschke
              stefan.eissing Stefan Eissing


              • Created:

                Issue deployment