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