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 "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2017/08/28 10:03:00 UTC

[jira] [Comment Edited] (OAK-6560) Sidegrade uses too much memory

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

Tomek Rękawek edited comment on OAK-6560 at 8/28/17 10:02 AM:
--------------------------------------------------------------

Fixed for trunk in [r1806378|https://svn.apache.org/r1806378], [r1806418|https://svn.apache.org/r1806418].


was (Author: tomek.rekawek):
Fixed for trunk in [r1806378|https://svn.apache.org/r1806378].

> Sidegrade uses too much memory
> ------------------------------
>
>                 Key: OAK-6560
>                 URL: https://issues.apache.org/jira/browse/OAK-6560
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: upgrade
>            Reporter: Tomek Rękawek
>            Assignee: Tomek Rękawek
>             Fix For: 1.8, 1.7.7
>
>         Attachments: OAK-6560.patch, OAK-6560.patch
>
>
> Repo migration from old segment to oak segment tar requires heap memory proportional to the repository size, which does not scale well for large-scale repositories. Also, some structures (e.g. lots of direct children) have a big impact on the memory footprint.
> For some repositories, the sidegrade requires as much as 40GB heap to perform the migration, which might not be an option for most of the customers.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)