[
https://issues.apache.org/jira/browse/OAK-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Saurabh updated OAK-6935:
-------------------------------
Fix Version/s: 1.8
> Active deletion logs warn messages when it tries to delete blobs already
> purged by DSGC
> ---------------------------------------------------------------------------------------
>
> Key: OAK-6935
> URL: https://issues.apache.org/jira/browse/OAK-6935
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Minor
> Fix For: 1.8, 1.7.12
>
>
> In cases when BlobGC deleted the blobs which active delete logic later came
> around to purge., active deletion logs a warn message. An example timeline
> would be:
> * t1 -> index blob gets deleted (active delete logic notes it down)
> * t2 -> compaction removes ref to this blob from node store
> * t3 (t1 + 24 hours) -> blob gc runs and collects the blob
> * t4 -> active gc tries to purge an already deleted blob
> (note, active delete runs between t1 and t3 would not delete the blobs as it
> hasn't be 24 hours since blob deletion).
> While this would happen for a small set of blobs (that are unfortunate to get
> compacted and cleaned up by DSGC before active deletion comes around) - but,
> the warn log is annoying. It would be useful to detect this case and not log
> warn on failure to delete for these.
> /cc [~amjain]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
