jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (OAK-4873) Avoid running GC too frequently
Date Wed, 21 Dec 2016 15:02:58 GMT

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

Michael Dürig resolved OAK-4873.
--------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.6)

Fixed at http://svn.apache.org/viewvc?rev=1775464&view=rev. 

If {{FileStore.gc()}} is now invoked more than once per 10 hours a warning will be logged
and gc will be skipped:

{noformat}
TarMK GC #2: skipping garbage collection as it already ran less than 10 hours ago (32 s).
{noformat}

The default backoff time of 10 hours can be set for debugging purposes via the {{gc.backoff}}
feature flag. 

> 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
>            Priority: Blocker
>              Labels: compaction, gc
>             Fix For: 1.5.17
>
>
> 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)

Mime
View raw message