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 "Francesco Mari (Jira)" <ji...@apache.org> on 2019/08/20 11:27:00 UTC
[jira] [Updated] (OAK-8066) Nodes with many direct children can
lead to OOME when saving
[ https://issues.apache.org/jira/browse/OAK-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Mari updated OAK-8066:
--------------------------------
Fix Version/s: 1.10.5
> Nodes with many direct children can lead to OOME when saving
> ------------------------------------------------------------
>
> Key: OAK-8066
> URL: https://issues.apache.org/jira/browse/OAK-8066
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Priority: Major
> Labels: TarMK
> Fix For: 1.12.0, 1.10.5
>
>
> {{DefaultSegmentWriter}} keeps a map of [child nodes|https://github.com/apache/jackrabbit-oak/blob/trunk/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/DefaultSegmentWriter.java#L805] of a node being written. This can lead to high memory consumption in the case where many child nodes are added at the same time. The latter could happen in the case where a node needs to be rewritten because of an increase in the GC generation from a concurrently completed revision garbage collection.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)