[
https://issues.apache.org/jira/browse/OAK-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Jain resolved OAK-3443.
----------------------------
Resolution: Fixed
Fix Version/s: 1.2.7
1.3.7
Fixed with
* trunk - r1705268, r1705273
* 1.0 - r1705288
* 1.2 - r1705312
> 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: Critical
> Labels: resilience
> Fix For: 1.3.7, 1.2.7, 1.0.22
>
>
> Similarly to what is done for a shared datastore in OAK-3360, the start time
> of the mark should be used as a reference for deletion of blobs in GC for
> 1.0.x. The problem is that in 1.0.x the mark iterated over the data store
> which could take a lot of time (many hours) and the buffer due to
> {{blobGcMaxAgeInSecs}} may get stale due to which data loss could happen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
