Terms or components
This feature introduces several new concepts. The meanings of these new concepts and terms are defined here. Other existing terms are also defined for clarity.
- Abort Incomplete MPU Reclamation Service
- Service mpu-space-reclamation service aborts all the incomplete multipart uploads for the current day. This service is also automatically started on access pools, which have expiration enabled vaults that are deployed.
- Abort Incomplete MPU Scanning Service
- Service mpu-scanning scans buckets for Initiated Multipart Upload Transactions that are expired and need to be aborted. Service is automatically started on access pools, which have expiration enabled vaults that are deployed.
- Byte Deletion Rate
- The maximum rate, in bytes per second, at which objects or incomplete multipart uploads can be deleted during the reclamation process. Can be set on a storage pool by using the object lifecycle configuration.
- Expired Object Delete Marker (EODM)
- A term to describe a delete marker whose object has no retained versions.
- Lifecycle Policy
- The collection of expiration rules that define which objects to be deleted and when. This operation is set by using the PUT ?lifecycle operation on a bucket.
- Object Deletion Rate
- The maximum rate, in objects per second, at which objects or incomplete multipart uploads can be deleted during the reclamation process. Can be set on a storage pool by using the object lifecycle configuration.
- Object Scan Rate
- The maximum rate, in objects per second, at which object metadata (for versioned and non-versioned objects) or incomplete multipart transactions can be read during the scanning process. Can be set on a storage pool by using the object lifecycle configuration.
- Reclamation Service
- Service expiration-space-reclamation deletes objects (versioned and non-versioned) for the current day. This service is also automatically started on access pools that have expiration enabled vaults that are deployed. This is an existing service that is used to expire objects currently for object expiration feature. It was simply extended to handle more object types.
- Scanning Services
- This operation is a set of 2 or 3 services that scan buckets for objects to be deleted. In vault mode, these services are vault-scanning-range-creation and lifecycle-name-index-scan. In container mode, these services are lifecycle-container-listing, container-scanning-range-creation, and lifecycle-name-index-scan. These services are automatically started on access pools with expiration-enabled vaults deployed.
- Version Scanning Services:
- This is a set of three services that scan buckets for objects to be deleted. In container mode, these services are lifecycle-container-listing, version-scanning-range-creation, and version-index-scan. These services are automatically started on access pools, which have expiration enabled vaults that are deployed.
- Work queues
- The scanning and reclamation services keep track of and communicate work to be done by using leasable work queues. These queues are the primary data structures that are used by the scanning and reclamation services to distributed work across multiple Accesser nodes.