[jira] [Resolved] (OAK-1772) Expose an extension point to move in memory state in UnsavedModification to persisted map

["Chetan Mehrotra (JIRA)" <ji...@apache.org>]

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

Chetan Mehrotra resolved OAK-1772.
----------------------------------

    Resolution: Fixed

Applied the patch in [r1590595|http://svn.apache.org/r1590595] to trunk and merged in [r1590596|http://svn.apache.org/r1590596] to 1.0 branch

> Expose an extension point to move in memory state in UnsavedModification to persisted map
> -----------------------------------------------------------------------------------------
>
>                 Key: OAK-1772
>                 URL: https://issues.apache.org/jira/browse/OAK-1772
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.0, 1.1
>
>         Attachments: OAK-1772-oak-mapdb-1.patch
>
>
> Currently DocumentNodeStore stores some state in {{org.apache.jackrabbit.oak.plugins.document.UnsavedModifications}} class related to branch commit. If number of branch commit are large (say in migration) then this state grows proportionally to the number of nodes getting added/modified in that branch and thus can cause OOM.
> To support such cases we can use a persisted map impl like mapdb [1]. To enable such usage an extension point need to be added in {{UnsavedModifications}} to change the impl
> [1] http://www.mapdb.org/



--
This message was sent by Atlassian JIRA
(v6.2#6252)