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

• Type: Sub-task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.2.6, 1.3.6, 1.4
• Component/s: blob
• Labels: resilience
• Assignee: Amit Jain
• Reporter: Amit Jain
• Created: 07/Sep/15 09:12
• Updated: 02/Mar/16 14:19
• Resolved: 11/Sep/15 08:03

Description

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.

Issue Links

• is cloned by: OAK-3443 Track the start time of mark in GC