[
https://issues.apache.org/jira/browse/OAK-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138920#comment-15138920
]
Vikas Saurabh commented on OAK-3710:
------------------------------------
bq. early cleanup removing its old property values
[~rosu], the cleanup I meant above was about removing dependency on commit
root. From document node state perspective, it shouldn't change anything (no
properties are cleaned up... also, the semantics of what's committed and what's
not would remain the same). The cleanup was essentially about:
* Initial state-> /a/b/@_commitRoot/@r123-0-2=0 and /@_revision/@r123-0-2="c"
//i.e. r123-0-2 is committed but to get that knowledge, we need to go back into
"/".
* clean up would remove /a/b/@_commitRoot/@r123-0-2 and would add
/a/b/@_revision/@r123-0-2="c" //thus r123-0-2 maintains its state of being
committed, we are just tryeing to remove back-link into "/"
* Note, that the clean would not clean up /@revision/@r123-0-2 just yet... it'd
have to be done separately.
Btw, the reason to require such cleanup (remove backlinks to commit-root) is
that split docs containing {{_revision.rX-Y-Z="c"}} on behalf of underlying
documents (due to backlinks) aren't cleaned up currently.
> 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)
