[OAK-2603] Failure in one of the batch in VersionGC might lead to orphaned nodes

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.13, 1.1.8
• Component/s: mongomk
• Assignee: Chetan Mehrotra
• Reporter: Chetan Mehrotra
• Created: 10/Mar/15 12:04
• Updated: 20/Apr/15 13:45
• Resolved: 11/Mar/15 10:43

Description

VersionGC logic currently performs deletion of nodes in batches. For GC to work properly NodeDocument should always be removed in bottom-up mode i.e. parent node should be removed after child has been removed

Currently the GC logic deletes the NodeDocument in undefined order. In such mode if one of the batch fails then its possible that parent might have got deleted but the child was not deleted.

Now in next run the child node would not be recognized as a deleted node because the commit root would not be found.

Issue Links

• is related to: OAK-2557 VersionGC uses way too much memory if there is a large pile of garbage