jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-8066) Nodes with many direct children can lead to OOME when saving
Date Thu, 21 Feb 2019 08:41:01 GMT

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

Michael Dürig commented on OAK-8066:
------------------------------------

One way to fix this is to regularly flush the accumulated child nodes into a map record. See [https://github.com/mduerig/jackrabbit-oak/tree/OAK-8066]
for WIP.

/cc  [~frm]

> 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
>
> {{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
(v7.6.3#76005)

Mime
View raw message