[
https://issues.apache.org/jira/browse/OAK-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-4494:
----------------------------------
Attachment: OAK-4494.patch
Proposed changes for MongoDocumentStore.
The patch introduces a ModificationStamp, which is a simple struct that
consists of the modCount and the modified timestamp with 5 seconds resolution.
It replaces the modCount parameter when the cache is invalidated.
An alternative approach was discussed offline as well. The modCount could be
initialized with a value that e.g. equals the current time millis. With MongoDB
this is not easily possible and would require additional calls when
MongoDocumentStore attempts to create documents. Initializing the modCount with
a timestamp also has the downside of loosing information how many times the
document was modified since it was created.
[~reschke] & [~catholicon], WDYT?
> Stale documents after revision GC in cluster
> --------------------------------------------
>
> Key: OAK-4494
> URL: https://issues.apache.org/jira/browse/OAK-4494
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, documentmk, mongomk, rdbmk
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
> Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4
> Fix For: 1.6
>
> Attachments: OAK-4494.patch
>
>
> Implement additional tests for revision GC in a cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
