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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2018/04/11 07:13:00 UTC

[jira] [Commented] (OAK-7401) Changes kept in memory when update limit is hit in commit hook

    [ https://issues.apache.org/jira/browse/OAK-7401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433505#comment-16433505 ] 

Marcel Reutegger commented on OAK-7401:
---------------------------------------

Added ignored test to trunk: http://svn.apache.org/r1828868

> Changes kept in memory when update limit is hit in commit hook
> --------------------------------------------------------------
>
>                 Key: OAK-7401
>                 URL: https://issues.apache.org/jira/browse/OAK-7401
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: documentmk
>    Affects Versions: 1.6.0, 1.8.0
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Major
>             Fix For: 1.10
>
>
> In some cases no persisted branch is created by the DocumentNodeStore when the number of changes hit the update limit. This happens when the current branch state is in-memory and the commit hook contributes changes that reach the update limit. The implementation keeps those changes in memory, which may lead to a commit way bigger than specified by the update limit.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)