Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-2263

Cluster-aware lock expiration

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      The current lock expiration mechanism is only able to expire locks on the cluster node where they were first added. This avoids nasty race conditions, but hides the expiration time (getRemainingTime) from other cluster nodes and breaks expiration of the lock if the originating cluster node is removed from the cluster.

      It would be nice to have a good cluster-wide lock expiration mechanism that doesn't end up with all cluster nodes trying to unlock expired locks at the same time.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              jukkaz Jukka Zitting
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: