[
https://issues.apache.org/jira/browse/OAK-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig resolved OAK-3602.
--------------------------------
Resolution: Won't Fix
This is fixed in {{oak-segment-next}} by the new cleanup strategy implemented
within OAK-3348.
> Remove the SegmentWriter segmentId from the cleanup set
> -------------------------------------------------------
>
> Key: OAK-3602
> URL: https://issues.apache.org/jira/browse/OAK-3602
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segmentmk
> Reporter: Alex Parvulescu
> Assignee: Alex Parvulescu
> Priority: Minor
> Labels: cleanup, gc
>
> It looks like the current head's segment id (coming from the SegmentWriter)
> is always passed to the cleanup's referenced segment ids set, even though it
> cannot be cleaned (similar to the TarWriter situation) so I propose removing
> it early from the mentioned set.
> benefits include making the cleanup set more stable (head changes quite often
> so the cleanup set is more volatile) which will help in figuring out if we
> still need to clean a specific tar file or not based on previous cleanup runs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
