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

["Alex Parvulescu (JIRA)" <ji...@apache.org>]

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

Alex Parvulescu edited comment on OAK-4410 at 5/30/16 2:48 PM:
---------------------------------------------------------------

fixed in trunk with r1746120, and reverted with r1746139.
The trouble here is with the fact that the change will produce new tar file generations too eagerly hitting the 'z' limit fast. one prerequisite of this would be to reconsider OAK-2193 which wold remove this artificial barrier.


was (Author: alex.parvulescu):
fixed in trunk with r1746120

> 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
>              Labels: candidate_oak_1_2, candidate_oak_1_4, cleanup, gc
>         Attachments: OAK-4410.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.4#6332)