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

Lease failure when update takes longer than socket timeout

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.44.0
    • mongomk
    • None

    Description

      The DocumentNodeStore may consider a lease update as failed when the operation takes longer than the socket timeout and later succeeds on MongoDB within the lease time. In this situation the lease mechanism currently thinks there was a lease update from another process and therefore backs off.

      The implementation keeps track of the last successful lease update and based on this information performs a conditional lease update. The implementation should be more tolerant when it encounters an 'unexpected' update within the lease period and still consider the lease valid.

      Attachments

        Activity

          People

            mreutegg Marcel Reutegger
            corderob José Andrés Cordero Benítez
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: