You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2014/04/24 18:34:14 UTC

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

     [ https://issues.apache.org/jira/browse/OAK-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated OAK-1768:
-------------------------------

    Attachment: 0001-OAK-1768-DocumentNodeBuilder.setChildNode-runs-OOM-w.patch

Attached a proposed patch based on earlier work in OAK-1760.

The {{NodeBuilder.setChildNode()}} method is not very widely used so the impact of this change isn't very big. The original key use case for this method was moving and copying of subtrees, but nowadays we have separate mechanisms for those operations which leaves this method mostly used by lower-level updates in a few commit hooks.

> 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.2#6252)