jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-7401) Changes kept in memory when update limit is hit in commit hook
Date Tue, 25 Jun 2019 07:43:00 GMT

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

Julian Reschke commented on OAK-7401:
-------------------------------------

trunk: (1.9.0) [r1829826|http://svn.apache.org/r1829826] [r1829824|http://svn.apache.org/r1829824]
[r1828868|http://svn.apache.org/r1828868]
1.8: (1.8.13) [r1855327|http://svn.apache.org/r1855327]
1.6: (1.6.17) [r1855331|http://svn.apache.org/r1855331]

> 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
>              Labels: candidate_oak_1_6, candidate_oak_1_8
>             Fix For: 1.9.0, 1.10.0
>
>
> 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)

Mime
View raw message