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/12/21 15:47:58 UTC
[jira] [Comment Edited] (OAK-4873) Avoid running GC too frequently
[ https://issues.apache.org/jira/browse/OAK-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767254#comment-15767254 ]
Michael Dürig edited comment on OAK-4873 at 12/21/16 3:47 PM:
--------------------------------------------------------------
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 {{oak.gc.backoff}} feature flag.
was (Author: mduerig):
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)