[
https://issues.apache.org/jira/browse/OAK-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-1648:
---------------------------------
Labels: resilience (was: candidate_oak_1_0 resilience)
Fix Version/s: 1.0.32
Merged to 1.0 with 1751284. This was required for tests of OAK-3436 to pass on
Mongo
> 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.4, 1.3.8, 1.2.10, 1.0.32
>
>
> 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)
