[
https://issues.apache.org/jira/browse/OAK-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996303#comment-15996303
]
Marcel Reutegger commented on OAK-5898:
---------------------------------------
No, this is not possible. The command checks the format version and refuses to
run in case it doesn't match. We could probably make it work. As you mentioned,
the Revision GC does not write new changes. I'm still a bit reluctant, because
I don't want users to start a habit of using an oak-run version that doesn't
match the repository. In my view the general recommendation should be to use
the same version and let oak-run enforce it.
I would prefer a backport of the command, if it turns out to be useful also for
older versions.
> 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)
