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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2016/09/22 09:10:20 UTC

[jira] [Assigned] (OAK-4371) Overly zealous warning about checkpoints on compaction

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

Michael Dürig reassigned OAK-4371:
----------------------------------

    Assignee: Michael Dürig

> Overly zealous warning about checkpoints on compaction 
> -------------------------------------------------------
>
>                 Key: OAK-4371
>                 URL: https://issues.apache.org/jira/browse/OAK-4371
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-tar, segmentmk
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: compaction, gc, logging
>             Fix For: Segment Tar 0.0.14
>
>
> {{FileStore.compact}} logs a warning {{TarMK GC #{}: compaction found {} checkpoints, you might need to run checkpoint cleanup}} if there is more than a single checkpoints. 
> AFIK this is now the norm as async indexing has uses 2 checkpoints ([~chetanm], [~edivad] please clarify). 
> In any case should we improve this and not hard code any number of expected checkpoints. Maybe make the threshold configurable?



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