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-6425) Make the CompositeNodeStore thread-safe
Date Thu, 06 Jul 2017 08:25:01 GMT

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

Tomek Rękawek commented on OAK-6425:

With regards to the read-only constraint - it's still in place, although I think it'd be good
to start hardening the implementation, so at some point in the future we may support multiple
read-write stores as well. It will be useful, eg. for content-aware sharding.

Since I was working on introducing the synchronization in this issue, I thought it'd be useful
to make it compatible with the RW stores. If the performance penalty is too big here, we may
rework the approach to work differently on RO and RW partial stores.

> Make the CompositeNodeStore thread-safe
> ---------------------------------------
>                 Key: OAK-6425
>                 URL: https://issues.apache.org/jira/browse/OAK-6425
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: composite
>            Reporter: Tomek Rękawek
>            Assignee: Tomek Rękawek
>             Fix For: 1.8, 1.7.4
> The CompositeNodeStore, unlike other *NodeStore implementations, is not thread safe (eg.
two concurrent merge() invocations may leave the repository in inconsistent state).

This message was sent by Atlassian JIRA

View raw message