jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Created: (JCR-2263) Cluster-aware lock expiration
Date Tue, 18 Aug 2009 15:19:14 GMT
Cluster-aware lock expiration
-----------------------------

                 Key: JCR-2263
                 URL: https://issues.apache.org/jira/browse/JCR-2263
             Project: Jackrabbit Content Repository
          Issue Type: Improvement
          Components: clustering, jackrabbit-core, locks
            Reporter: Jukka Zitting
            Priority: Minor


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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message