jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-2472) Add support for atomic counters on cluster solutions
Date Mon, 11 Jan 2016 10:26:40 GMT

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

Marcel Reutegger commented on OAK-2472:

One reason why consolidation tasks are re-created may be due to the retry logic in DocumentNodeStoreBranch.
When a commit fails because of a conflict, it is suspended until the conflicting change is
visible, then changes are rebased and a new commit is attempted. This also means the commit
hook is called again and I assume the atomic counter editor will again create a new consolidation

You can track conflict handling when you enable debug logging for the classes DocumentNodeStoreBranch
and Collision.

> Add support for atomic counters on cluster solutions
> ----------------------------------------------------
>                 Key: OAK-2472
>                 URL: https://issues.apache.org/jira/browse/OAK-2472
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.3.0
>            Reporter: Davide Giannella
>            Assignee: Davide Giannella
>              Labels: scalability
>             Fix For: 1.4
>         Attachments: atomic-counter.md, oak-1452185608.log.gz, oak-1452268140.log.gz
> As of OAK-2220 we added support for atomic counters in a non-clustered situation. 
> This ticket is about covering the clustered ones.

This message was sent by Atlassian JIRA

View raw message