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

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

Created a PR with proposed fix: https://github.com/apache/jackrabbit-oak/pull/84

> 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.0, 1.2, 1.4, 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)

Reply via email to