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/10/18 08:37:59 UTC

[jira] [Resolved] (OAK-4873) Avoid running GC too frequently

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

Michael Dürig resolved OAK-4873.
--------------------------------
       Resolution: Won't Fix
    Fix Version/s:     (was: Segment Tar 0.0.16)

I agree with [~alex.parvulescu]: the estimator does and should provide this functionality. After all, any SNFE caused by a bad configuration and running gc too often is transient. 

> 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
>
> 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
(v6.3.4#6332)