[OAK-4780] VersionGarbageCollector should be able to run incrementally

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.7.0, 1.8.0
• Component/s: documentmk
• Epic Link: DocumentMK revision GC
• Assignee: Unassigned
• Reporter: Julian Reschke
• Created: 08/Sep/16 14:42
• Updated: 28/Jun/19 13:24
• Resolved: 17/Apr/17 11:32

Description

Right now, the documentmk's version garbage collection runs in several phases.

It first collects the paths of candidate nodes, and only once this has been successfully finished, starts actually deleting nodes.

This can be a problem when the regularly scheduled garbage collection is interrupted during the path collection phase, maybe due to other maintenance tasks. On the next run, the number of paths to be collected will be even bigger, thus making it even more likely to fail.

We should think about a change in the logic that would allow the GC to run in chunks; maybe by partitioning the path space by top level directory.

Issue Links

• is blocked by: OAK-6020 add a Guava Stopwatch like duration formatter
• is related to: OAK-8448 VersionGC may get stuck at 60s scope
• is related to: OAK-5898 Revision GC command line tool
• is related to: OAK-3070 Use a lower bound in VersionGC query to avoid checking unmodified once deleted docs
• is related to: OAK-5571 VersionGarbageCollector can remove leaf nodes eagerly
• is related to: OAK-6083 RDBDocumentStore: implement support for VersionGCSupport extensions added for OAK-4780
• is related to: OAK-6059 Revert VersionGC supplier change