[OAK-1768] DocumentNodeBuilder.setChildNode() runs OOM with large tree

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0
• Fix Version/s: 1.0.7, 1.1.0
• Component/s: core
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 24/Apr/14 12:44
• Updated: 16/Jul/15 08:33
• Resolved: 25/Sep/14 07:24

Description

This is a follow up issue for OAK-1760. There we implemented a workaround in the upgrade code to prevent the OOME. For the 1.1 release we should implement a proper fix in the DocumentNodeStore as suggested by Jukka in OAK-1760.

Issue Links

• is related to: OAK-1760 RepositoryUpgrade leads to one large commit with DocumentNodeStore causing OOM
• is related to: OAK-3112 Performance degradation of UnsavedModifications on MapDB
• is related to: OAK-2131 Reduce usage of _lastRev
• relates to: OAK-2513 algorithm with O(n!) in mongoMk rebase - not finishing in years
• relates to: OAK-2324 Remove dependency to MapDB