[
https://issues.apache.org/jira/browse/OAK-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127031#comment-14127031
]
Marcel Reutegger commented on OAK-1768:
---------------------------------------
Committed work in progress in http://svn.apache.org/r1623827
remove() and setChildNode() are now applied recursively and leverage the
MongoMK branch mechanism.
The remaining problem is with tracking the affected paths of a branch commit.
When a branch is merged, all documents for the affected paths of the merge must
be updated and the _lastRev must be set to the merge commit revision. This is
currently kept in memory within UnsavedModifications.
> DocumentNodeBuilder.setChildNode() runs OOM with large tree
> -----------------------------------------------------------
>
> Key: OAK-1768
> URL: https://issues.apache.org/jira/browse/OAK-1768
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Affects Versions: 1.0
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Fix For: 1.1
>
> Attachments:
> 0001-OAK-1768-DocumentNodeBuilder.setChildNode-runs-OOM-w.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
