[ https://issues.apache.org/jira/browse/OAK-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996386#comment-15996386 ]
Chetan Mehrotra commented on OAK-5898: -------------------------------------- bq. There may be more dependencies, but in general the command just triggers the GC and therefore isn't that complex. Thats helpful to know. Keeps the backport option open! > 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 > Fix For: 1.7.0, 1.8 > > > 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 (v6.3.15#6346)