You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (Jira)" <ji...@apache.org> on 2022/05/10 16:50:00 UTC
[jira] [Resolved] (OAK-9765) Garbage Collection does not remove blobs file from the file system
[ https://issues.apache.org/jira/browse/OAK-9765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved OAK-9765.
-----------------------------------
Resolution: Invalid
AFAICS the test does not run compaction on the SegmentNodeStore. This means the blob is still reference by a segment even if the property has been deleted. The test needs to run a full compaction on the SegmentNodeStore before a blob garbage collection is triggered. Only then will the unused blob be removed.
> Garbage Collection does not remove blobs file from the file system
> ------------------------------------------------------------------
>
> Key: OAK-9765
> URL: https://issues.apache.org/jira/browse/OAK-9765
> Project: Jackrabbit Oak
> Issue Type: Bug
> Affects Versions: 1.42.0
> Reporter: Piercarlo Slavazza
> Priority: Blocker
>
> Using a NodeStore backed by a FileStore, with a blob store of type FileBlobStore:
> # (having configured GC with estimation {_}disabled{_})
> # a file is added as a blob
> # then the node where the blob is references is _removed_
> # then the GC is run
> # expected behaviour: the node is no more accessible, _and_ no chunk of the blob is present on the file system
> # actual behaviour: the node is no more accessible BUT all the chunks are still present on the file system
> Steps to reproduce: execute the (really tiny) main in [https://github.com/PiercarloSlavazza/oak-garbage-collection-test/] (instructions in the readme)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)