Mailing-List: contact oak-issues-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Date: Thu, 1 Dec 2016 11:18:58 +0000 (UTC)
From: "Stefan Egli (JIRA)" <jira@apache.org>
To: oak-issues@jackrabbit.apache.org
Message-ID: <JIRA.12936309.1454495810000.411815.1480591138368@Atlassian.JIRA>
In-Reply-To: <JIRA.12936309.1454495810000@Atlassian.JIRA>
References: <JIRA.12936309.1454495810000@Atlassian.JIRA> <JIRA.12936309.1454495810185@arcas>
Subject: [jira] [Comment Edited] (OAK-3976) journal should support large(r)
 entries
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 01 Dec 2016 11:19:05 -0000


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

Stefan Egli edited comment on OAK-3976 at 12/1/16 11:18 AM:
------------------------------------------------------------

[~mreutegg], [~catholicon], [~chetanm], [~reschke], I think I won't find time to do this atm, would one of you (or someone else) be able to cover this? thx!
ping :)


was (Author: egli):
[~mreutegg], [~catholicon], [~chetanm], [~reschke], I think I won't find time to do this atm, would one of you (or someone else) be able to cover this? thx!

> journal should support large(r) entries
> ---------------------------------------
>
>                 Key: OAK-3976
>                 URL: https://issues.apache.org/jira/browse/OAK-3976
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk
>    Affects Versions: 1.3.14
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>             Fix For: 1.6, 1.5.15
>
>
> Journal entries are created in the background write. Normally this happens every second. If for some reason there is a large delay between two background writes, the number of pending changes can also accumulate. Which can result in (arbitrary) large single journal entries (ie with large {{_c}} property).
> This can cause multiple problems down the road:
> * journal gc at this point loads 450 entries - and if some are large this can result in a very large memory consumption during gc (which can cause severe stability problems for the VM, if not OOM etc). This should be fixed with OAK-3001 (where we only get the id, thus do not care how big {{_c}} is)
> * before OAK-3001 is done (which is currently scheduled after 1.4) what we can do is reduce the delete batch size (OAK-3975)
> * background reads however also read the journal entries and even if OAK-3001/OAK-3975 are implemented the background read can still cause large memory consumption. So we need to improve this one way or another.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)