[
https://issues.apache.org/jira/browse/OAK-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346239#comment-15346239
]
Marcel Reutegger commented on OAK-4494:
---------------------------------------
Oops, good catch.
When I change it to MODIFIED_IN_SECS the test fails because the modified
timestamp does not change in the test. There is a virtual clock, but it is not
used by the Revision in the test.
I think it would be good to also ensure the revision GC runs with a
maxRevisionAge that does not result in resurrected documents with the same
modified timestamp. I'll open a separate issue about that.
> 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)
