[
https://issues.apache.org/jira/browse/OAK-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13716332#comment-13716332
]
Michael Dürig commented on OAK-927:
-----------------------------------
This should be fixed at revision 1505988.
I leave the issue open until we have further confirmation.
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
