You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2019/01/14 08:31:00 UTC

[jira] [Commented] (OAK-7976) Non-blocking commit rollback

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

Marcel Reutegger commented on OAK-7976:
---------------------------------------

I moved the inefficient rollback to a separate issue OAK-7984.

> Non-blocking commit rollback
> ----------------------------
>
>                 Key: OAK-7976
>                 URL: https://issues.apache.org/jira/browse/OAK-7976
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Major
>             Fix For: 1.12
>
>
> When a commit fails e.g. due to a conflict, the changes are rolled back while still holding the commit revision. This causes an unnecessary delay for other commits because at this point it is certain that the revision associated with the rolled back changes will never commit.
> The current implementation is also inefficient because it rolls back the changes one document at a time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)