Mailing-List: contact oak-issues-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Date: Thu, 1 Jun 2017 08:43:04 +0000 (UTC)
From: "Alex Parvulescu (JIRA)" <jira@apache.org>
To: oak-issues@jackrabbit.apache.org
Message-ID: <JIRA.12973949.1464608268000.339647.1496306584535@Atlassian.JIRA>
In-Reply-To: <JIRA.12973949.1464608268000@Atlassian.JIRA>
References: <JIRA.12973949.1464608268000@Atlassian.JIRA> <JIRA.12973949.1464608268227@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (OAK-4410) More aggressive cleanup for offline
 compaction
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 01 Jun 2017 08:43:08 -0000


     [ https://issues.apache.org/jira/browse/OAK-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Parvulescu resolved OAK-4410.
----------------------------------
    Resolution: Won't Fix

don't plan to work on this, if there's interest, the patch is attached to this issue.

> More aggressive cleanup for offline compaction
> ----------------------------------------------
>
>                 Key: OAK-4410
>                 URL: https://issues.apache.org/jira/browse/OAK-4410
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segmentmk
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>         Attachments: OAK-4410.patch, OAK-4410-v2.patch
>
>
> In the case where a segment store doesn't use an external datastore, running offline compaction can result in a slight increase of the overall size, due to the cleanup threshold check present in the TarReader.
> I think we need to be more aggressive with GC for offline compaction (basically reduce the threshold to zero), this would give more predictable results in terms of size.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)