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-7758) Non-blocking CompositeNodeStore merges
Date Tue, 02 Oct 2018 09:01:00 GMT

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

Michael Dürig commented on OAK-7758:

>From the top of my head this was designed for a single writeable store only. The concern
with multiple writeable stores was consistency guarantees in the face of failures. I.e. how
would a commit that succeeded on a first store but subsequently failed on the second store
be handled? How would we guarantee the repository is left in a consistent state afterwards?


> Non-blocking CompositeNodeStore merges
> --------------------------------------
>                 Key: OAK-7758
>                 URL: https://issues.apache.org/jira/browse/OAK-7758
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: composite
>            Reporter: Marcel Reutegger
>            Priority: Major
>             Fix For: 1.10
> The CompositeNodeStore serializes all merges with a lock. This prevents concurrent processing
of merges by the DocumentNodeStore.

This message was sent by Atlassian JIRA

View raw message