[ https://issues.apache.org/jira/browse/OAK-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amit Jain updated OAK-3443: --------------------------- Fix Version/s: (was: 1.2.6) (was: 1.3.6) 1.0.22 > Track the start time of mark in GC > ---------------------------------- > > Key: OAK-3443 > URL: https://issues.apache.org/jira/browse/OAK-3443 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: blob > Reporter: Amit Jain > Assignee: Amit Jain > Priority: Minor > Labels: resilience > Fix For: 1.0.22 > > > 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)