jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-6425) Make the CompositeNodeStore thread-safe
Date Thu, 06 Jul 2017 09:13:00 GMT

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

Michael Dürig commented on OAK-6425:

bq.  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

I wouldn't do this as supporting multiple rw stores is an entirely different story and can't
be done just in passing. To ensure our constraints we would need some sort of ACP (e.g 2PC)
here. A simple lock won't do.

> 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