[
https://issues.apache.org/jira/browse/OAK-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16815284#comment-16815284
]
Julian Reschke commented on OAK-5898:
-------------------------------------
trunk: (1.7.0) [r1794337|http://svn.apache.org/r1794337]
[r1792756|http://svn.apache.org/r1792756]
[r1792594|http://svn.apache.org/r1792594]
[r1792587|http://svn.apache.org/r1792587]
[r1792586|http://svn.apache.org/r1792586]
[r1792471|http://svn.apache.org/r1792471]
[r1792456|http://svn.apache.org/r1792456]
[r1792067|http://svn.apache.org/r1792067]
> Revision GC command line tool
> -----------------------------
>
> Key: OAK-5898
> URL: https://issues.apache.org/jira/browse/OAK-5898
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: documentmk, run
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Major
> Fix For: 1.7.0, 1.8.0
>
>
> Revision GC can be triggered on a DocumentNodeStore on each node in a
> cluster. A common setup with Apache Sling on top of Oak has a scheduled task
> for the leader node in a cluster that triggers the Revision GC once a day.
> For testing, maintenance and operational purpose it would be good to have an
> alternative that can be triggered from the command line.
> A potential solution is a new run mode in oak-run. It would bootstrap a
> DocumentStore implementation (MongoDB or RDB) with a read-only
> DocumentNodeStore and run revision GC. The command should probably support
> options like:
> - maxRevisionAge as defined in VersionGarbageCollector.gc()
> - maxGCTime that limits the time GC will run until it will be canceled
> automatically.
> - delay as proposed in OAK-4780
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
