-
Type: Improvement
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: BlobManager
-
Release Notes Summary:A new 'nuxeo.s3storage.s3DirectUpload.bucket_prefix' conf property is available to specify the bucket prefix of the blobProvider backing the transientStore used by the s3 batchHandler
-
Tags:
-
Team:PLATFORM
-
Sprint:nxplatform #72
-
Story Points:2
The bucket_prefix property if s3DirectUploadBlobProviderDestination is not configurable:
This is an issue when using several different Nuxeo apps, each of them using their own S3 bucket prefix. Nuxeo presales use a shared bucket/region (to avoid reaching the max 100 buckets limit we have on this account).
The fact that this BlobProvider is not configurable for the prefix leads to the following issue: A user uploads a file in demo #1, then the GC of Demo#2 cleans it up. So, the GC of demos#1 logs a
[org.nuxeo.ecm.core.blob.LocalBlobStore] Unknown blob for key: d7180165c77ad86d6df61e922a3513f7
and after some weeks/months, we have dozens of lines filling the log.
Notice https://jira.nuxeo.com/browse/NXP-30560 does not fix this, it fixes the issue for several providers of the same Nuxeo app)