[jira] [Commented] (OAK-3360) Tracking the start time of mark in GC for a shared datastore

["Amit Jain (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740433#comment-14740433 ] 

Amit Jain commented on OAK-3360:
--------------------------------

Slight change in test expectations for intermittent test failures
* 1.2 - http://svn.apache.org/r1702405
* trunk - http://svn.apache.org/r1702405

Thanks [~frm] for flagging.

> Tracking the start time of mark in GC for a shared datastore
> ------------------------------------------------------------
>
>                 Key: OAK-3360
>                 URL: https://issues.apache.org/jira/browse/OAK-3360
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>          Components: blob
>            Reporter: Amit Jain
>            Assignee: Amit Jain
>            Priority: Minor
>              Labels: resilience
>             Fix For: 1.3.6, 1.2.5
>
>
> Currently, for GC in a shared datastore, the last modified timestamp of the earliest references file is used to calculate the max age of blobs to be deleted. There is a possibility that the  process itself could have taken quite a long time which opens up a window that recent blobs could also be deleted. 
> The mark process is quite fast and with the default setting of {{blobGcMaxAgeInSecs}} of 24 hours this should not be a problem but if the {{blobGcMaxAgeInSec}} is specified to a lower value then it could create that window described above.



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