Deployment
This feature is first enabled on a storage pool level, at which point scan or delete rates are set. After that, the user can enable object expiration on individual vaults on the storage pool. Finally, the user can add lifecycle policies to each bucket with expiration that is enabled by using the S3 PUT bucket lifecycle API.
Since the scanning and reclamation services are run on the access pools, it is best to have each access pool deploy vaults from only one storage pool (rather than multiple storage pools). However, there is nothing that prevents the user from deploying in such a manner.
Setting the scan and delete rates is an important step in this process. When first enabling the
feature, there are suggested rates to be filled in and completed. In many cases, these rates are
suitable.
Note: Incidents are raised on the Manager if scanning or deletion takes longer than 18
hours, which allows the operator to know when the rates are set too low.
There is a known issue in which an Accesser crashes or restarts during a cycle can cause a relatively small number of object deletions to be delayed up to 72 hours. In order to prevent this from happening during upgrades, we recommend timing Accesser upgrades such that they occur after deletion finishes (that is, between 18:00 – 0:00 UTC).