[jira] [Resolved] (OAK-1648) Creating multiple checkpoint on same head revision overwrites previous entries

["Marcel Reutegger (JIRA)" <ji...@apache.org>]

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

Marcel Reutegger resolved OAK-1648.
-----------------------------------
    Resolution: Fixed

Fixed in trunk: http://svn.apache.org/r1707331

Changed the return value of the checkpoint() method within the bounds of the contract. Previously the method returned the exact head revision as currently set in the DocumentNodeStore. Now the method returns a unique revision which represents a state of the repository between the time when the method was called and when it returns.

> Creating multiple checkpoint on same head revision overwrites previous entries
> ------------------------------------------------------------------------------
>
>                 Key: OAK-1648
>                 URL: https://issues.apache.org/jira/browse/OAK-1648
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: mongomk
>            Reporter: Chetan Mehrotra
>            Assignee: Marcel Reutegger
>            Priority: Minor
>              Labels: resilience
>             Fix For: 1.3.8
>
>
> Currently when a checkpoint is created in DocumentNodeStore then it is saved in form of currentHeadRev=>expiryTime. Now if multiple checkpoints are created where head revision has not changed then only the last one would be saved and previous entries would be overridden as revision is used as key
> One fix would be to change the expiry time only if the new expiry time is greater than previous entry. However doing that safely in a cluster (check then save) is currently not possible with DocumentStore API as the modCount check if only supported for Nodes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)