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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2013/11/12 12:31:24 UTC

[jira] [Updated] (OAK-927) Concurrent commits may cause duplicate observation events

     [ https://issues.apache.org/jira/browse/OAK-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dürig updated OAK-927:
------------------------------

    Labels: observation  (was: )

> Concurrent commits may cause duplicate observation events
> ---------------------------------------------------------
>
>                 Key: OAK-927
>                 URL: https://issues.apache.org/jira/browse/OAK-927
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>          Components: core
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: observation
>             Fix For: 0.9
>
>
> Chetan discovered that in some cases spurious observation events would be created when to sessions save concurrently. In a nutshell the problem occurs since the current implementation of observation expects a linear sequence of revisions (per cluster node). However on Root.commit there is a small race between rebasing and merging a branch: when another session saves inside this time frame, its branch will have the same base revision like that of the former session. In this case the sequence of revisions is effectively non linear.
> Full discussion: http://markmail.org/message/cbzrztagurplxo4r



--
This message was sent by Atlassian JIRA
(v6.1#6144)