jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-4112) Replace the query exclusive lock with a cache tracker
Date Fri, 27 May 2016 12:17:12 GMT

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

Julian Reschke commented on OAK-4112:

As long as this change is not backported to 1.4...1.0, we should also add synchronization
to the existing BloomFilter related code in {{RDBDocumentStore}}. Will open a separate ticket
to track this.

> 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
>            Assignee: Tomek Rękawek
>              Labels: performance
>             Fix For: 1.6, 1.5.2
>         Attachments: OAK-4112-1.patch, OAK-4112-2.patch, OAK-4112-3.patch, OAK-4112-4.patch,
OAK-4112-putifnewer.patch, 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

View raw message