[
https://issues.apache.org/jira/browse/OAK-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138806#comment-15138806
]
Teodor Rosu commented on OAK-3710:
----------------------------------
[~catholicon] Wouldn’t this early document cleanup create a MVCC issue when:
- 2 oak nodes
- oak1 has an older root RevisionVector, example: due to clock issues
backgroundRead takes a lot ( e.g. blocked in
DocumentNodeStore.alignWithExternalRevisions )
- meanwhile oak2 commits property changes in /some_resource, does early cleanup
removing its old property values, while oak1 may still try to read these old
revisions/properties
> Continuous revision GC
> ----------------------
>
> Key: OAK-3710
> URL: https://issues.apache.org/jira/browse/OAK-3710
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core, documentmk
> Reporter: Marcel Reutegger
>
> Implement continuous revision GC cleaning up documents older than a given
> threshold (e.g. one day). This issue is related to OAK-3070 where each GC run
> starts where the last one finished.
> This will avoid peak load on the system as we see it right now, when GC is
> triggered once a day.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
