[OAK-1981] Implement full scale Revision GC for DocumentNodeStore

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Component/s: mongomk
• Labels: resilience scalability
• Assignee: Marcel Reutegger
• Reporter: Chetan Mehrotra
• Created: 23/Jul/14 06:54
• Updated: 02/Dec/15 10:59
• Resolved: 02/Dec/15 10:58

Description

So far we have implemented garbage collection in some form with OAK-1341. Those approaches help us remove quite a bit of garbage (mostly due to deleted nodes) but till some part is left

However full GC is still not performed due to which some of the old revision related data cannot be GCed like

• Revision info present in revision maps of various commit roots
• Revision related to unmerged branches (OAK-1926)
• Revision data created to property being modified by different cluster nodes

So having a tool which can perform above GC would be helpful. For start we can have an implementation which takes a brute force approach and scans whole repo (would take quite a bit of time) and later we can evolve it. Or allow system admins to determine to what level GC has to be done

Issue Links

• is blocked by: OAK-2392 [DocumentMK] Garbage Collect older revisions of binary properties in main document

Sub-Tasks

• Clean up orphaned branches: Closed