We have Nexus Repository 3.76.0, and would like to change the value of the “Expiration Days” for a S3 blob store.
The configuration page has a message on the very top, which reads: Updating the blob store configuration will cause it to be temporarily unavailable for a short period of time. Edits to configuration may also leave the blob store in a non-functional state.
Please correct me if I’m wrong. I’m believe that updating the Expiration Days will not make it non-functional. I only need to worry about the blob store becomes temporarily unavailable when making the change.
To plan for the change, we would need to understand the impact first. During the period of unavailable, what functionalities will be affected? How do we estimate the time required to complete the change?
We discovered a bug in this feature and removed it, I don’t recall which release it was delivered but the new approach is to set a time period in the Compact Blob Store task.
Non-functional should only happen if you make modifications which are invalid and result in being unable to interact with s3. Regardless though the blob store is taken temporarily offline which may interrupt downloads, and new downloads will fail during the offline period. (It should be very brief)
Before release 3.80.0, the Admin - Compact blob store task did not delete components from AWS S3 blob stores. As of release 3.80.0, AWS S3 blob stores uses the "Blobs Older Than " property for files in the S3 bucket. The S3 blob store configuration with the Expiration Days fields is no longer used for the S3 lifecycle policy.
The task only works on S3 blob store on 3.80 and above. The older version of the documentation available via Internet Archive Wayback Machine says:
AWS S3-based blob stores use a bucket lifecycle policy managed on the S3 blob store configuration to delete components. When components are soft-deleted using cleanup policies, the expiration days property sets the lifecycle on the blob in the S3 bucket.
The compact blob store task is not used for S3 blob stores.
Since we are using 3.76, I believe this task is not going to do anything with the S3 blob store.
Is the downtime on 3.76 before the Compact Blob Store task change was introduced expected to be very brief as well?