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 "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2017/06/01 08:43:04 UTC

[jira] [Resolved] (OAK-4410) More aggressive cleanup for offline compaction

     [ 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)