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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2016/06/23 10:45:16 UTC

[jira] [Updated] (OAK-4498) Introduce lower limit for gc() maxRevisionAge

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

Marcel Reutegger updated OAK-4498:
----------------------------------
    Summary: Introduce lower limit for gc() maxRevisionAge  (was: Lower limit for gc() maxRevisionAge)

> Introduce lower limit for gc() maxRevisionAge
> ---------------------------------------------
>
>                 Key: OAK-4498
>                 URL: https://issues.apache.org/jira/browse/OAK-4498
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, documentmk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.6
>
>
> Introduce and enforce a lower limit for maxRevisionAge in VersionGarbageCollector.gc().
> OAK-4494 changes the way documents in a cache are considered up-to-date. In addition to the modCount value it also considers the modified timestamp. To work properly, a new document must have a modified timestamp that is different from a previous incarnation (i.e. before gc removed it). The version GC should therefore not remove documents with a maxRevisionAge less than the modified resolution (5 seconds).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)