jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomek Rękawek (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-4112) Replace the query exclusive lock with a cache tracker
Date Wed, 09 Mar 2016 12:06:40 GMT

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

Tomek Rękawek commented on OAK-4112:
------------------------------------

[~mreutegg], [~chetanm], could you take a look on the description/patch and say if this approach
makes sense?

> Replace the query exclusive lock with a cache tracker
> -----------------------------------------------------
>
>                 Key: OAK-4112
>                 URL: https://issues.apache.org/jira/browse/OAK-4112
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk, mongomk
>            Reporter: Tomek Rękawek
>             Fix For: 1.6
>
>         Attachments: OAK-4112.patch
>
>
> The {{MongoDocumentStore#query()}} method uses an expensive {{TreeLock#acquireExclusive}}
method, introduced in OAK-1897 to avoid caching outdated documents.
> It should be possible to avoid acquiring the exclusive lock, by tracking the cache changes
that occurs during the Mongo find() operation. When the find() is done, we can update the
cache with the received documents if they haven't been invalidated in the meantime.



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

Mime
View raw message