-
Type:
Bug
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 2021.38
-
Component/s: BlobManager
-
Tags:
-
Team:PLATFORM
-
Sprint:nxplatform next
-
Story Points:5
As described in NXP-32180, an S3BlobProvider using a S3 bucket with versioning enabled AND with a KeyStrategyDocId (such as the record blob provider) stores blobs in a s3 bucket with keys of the form :
{providerId}:{docId}@{versionId}
However, when scrolling the blobs of such a provider, we only list the objects of the bucket (not each version) and we end up with keys like:
{providerId}:{docId}
which produces invalid keys that are not garbage collected (i.e. ignored) during a Full GC.
However, the record blob provider does not create orphaned blobs as mentioned in NXP-32787, and should not be garbage collected anyway.
- is related to
-
NXP-32787 Do not scroll record blob provider by default when triggering Full GC
-
- Open
-