[
https://issues.apache.org/jira/browse/OAK-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mete Atamel resolved OAK-488.
-----------------------------
Resolution: Fixed
Fixed in rev 1415108
> Concurrency issue with FetchCommitsAction
> -----------------------------------------
>
> Key: OAK-488
> URL: https://issues.apache.org/jira/browse/OAK-488
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
> Reporter: Mete Atamel
> Assignee: Mete Atamel
> Priority: Minor
>
> FetchCommitsAction is supposed to fetch all valid commits but it doesn't
> quite work correctly in concurrent scenarios. For example, imagine two MKs,
> one writing under a and the other under b in this order:
> 1- +/a0
> 2- +/b0
> 3- +/a0/a1
> 4- +/b0/b1
> After step1, step2 and step3 proceed concurrently. At step3,
> FetchCommitsAction returns rev0 and rev2 as valid revisions because at step2,
> rev2 was created from rev0 and it's currently valid. This is wrong because
> rev1 is also valid at the moment. So, step3 fails because /a0 cannot be found.
--
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
