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 "Andrei Dulceanu (JIRA)" <ji...@apache.org> on 2016/08/12 13:08:20 UTC

[jira] [Updated] (OAK-4669) Cleanup creates new generation of tar file without removing any segments

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

Andrei Dulceanu updated OAK-4669:
---------------------------------
    Attachment: test case.patch

Attached a simple test case to validate the hypothesis in the description.

> Cleanup creates new generation of tar file without removing any segments 
> -------------------------------------------------------------------------
>
>                 Key: OAK-4669
>                 URL: https://issues.apache.org/jira/browse/OAK-4669
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segment-tar
>    Affects Versions: Segment Tar 0.0.8
>            Reporter: Andrei Dulceanu
>            Assignee: Andrei Dulceanu
>            Priority: Minor
>              Labels: cleanup, gc
>             Fix For: Segment Tar 0.0.10
>
>         Attachments: test case.patch
>
>
> On some deployments I have seen tar files with a quite hight generation post-fix (e.g. 'v'). From the log files I could deduce that this particular tar file was rewritten multiple times without actually any segment being removed.
> I assume this is caused by the 25% gain threshold not taking the sizes contributed by the index and the graph entries into account.
> The attached test case can be used to verify the above hypothesis



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