You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/03/25 17:57:53 UTC

[jira] [Commented] (OAK-2681) Update lease without holding lock

    [ https://issues.apache.org/jira/browse/OAK-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380222#comment-14380222 ] 

Stefan Egli commented on OAK-2681:
----------------------------------

Related to OAK-2682 which would like to introduce a WARN if the clock in a cluster is off by too much.

> Update lease without holding lock
> ---------------------------------
>
>                 Key: OAK-2681
>                 URL: https://issues.apache.org/jira/browse/OAK-2681
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, mongomk
>            Reporter: Marcel Reutegger
>             Fix For: 1.1.8
>
>
> A lease update of the DocumentNodeStore on MongoDB will acquire a lock in MongoDocumentStore to perform the changes. The locking is only necessary for changes in the 'nodes' collection, because only those documents are cached and the locking makes sure the cache is consistent. The MongoDocumentStore must be changed to only acquire a lock when changes are done in the 'nodes' collection.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)