jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-4873) Avoid running GC too frequently
Date Tue, 18 Oct 2016 08:18:58 GMT

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

Alex Parvulescu commented on OAK-4873:

I think we can use the estimation check as a way to reduce the frequency of compactions. if
someone needs to test anything they are free to change the settings, otherwise running gc
too often should be a cheap noop and estimation can provide this protection.

> Avoid running GC too frequently
> -------------------------------
>                 Key: OAK-4873
>                 URL: https://issues.apache.org/jira/browse/OAK-4873
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-tar
>    Affects Versions: Segment Tar 0.0.16
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: compaction, gc
>             Fix For: Segment Tar 0.0.16
> As {{RevisionGCMBean.startRevisionGC()}} can be used to manually invoke a gc cycle, there
is the danger of running into a {{SNFE}} when gc is run multiple times in quick succession
(due to the retention time being based on number of generations). We should come up with a
mechanism to prevent this scenario. 

This message was sent by Atlassian JIRA

View raw message