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 "Davide Giannella (JIRA)" <ji...@apache.org> on 2016/11/14 11:36:01 UTC
[jira] [Closed] (OAK-5029) Use head GC generation number to trigger
cleanup on standby instance
[ https://issues.apache.org/jira/browse/OAK-5029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davide Giannella closed OAK-5029.
---------------------------------
Bulk close for 1.5.13
> Use head GC generation number to trigger cleanup on standby instance
> ---------------------------------------------------------------------
>
> Key: OAK-5029
> URL: https://issues.apache.org/jira/browse/OAK-5029
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Affects Versions: Segment Tar 0.0.16
> Reporter: Timothee Maret
> Assignee: Francesco Mari
> Fix For: 1.6, 1.5.13
>
> Attachments: OAK-5029.patch
>
>
> With {{oak-segment-tar}}, the trigger for running {{cleanup}} on the standby instance could be determined by the GC generation number of the head which is bound to increase every time a cleanup is ran.
> {code}
> fileStore.getHead().getRecordId().getSegment().getGcGeneration();
> {code}
> The current trigger mechanism consists of detecting a 25% size increase over a client cycle (typ. 5 sec).
> This would be dropped in favor of the new detection mechanism.
> The auto-compaction mode would remain configurable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)