The Complete Multipart Upload operation completes a multipart upload of an object by assembling the previously uploaded parts.
Conflicting client requests, such as two clients writing to the same key, are resolved on a latest-wins
basis. The timing for the latest-wins
evaluation is based on when the StorageGRID system completes a given request, and not on when S3 clients begin an operation.
StorageGRID supports objects up to 5 TB in size.
The x-amz-storage-class request header is supported, and affects how many object copies StorageGRID creates if the matching ILM rule specifies an Ingest Behavior of Dual commit or Balanced.
(Default) Specifies a dual-commit ingest operation when the ILM rule uses the Dual commit option, or when the Balanced option falls back to creating interim copies.
Specifies a single-commit ingest operation when the ILM rule uses the Dual commit option, or when the Balanced option falls back to creating interim copies.
This operation completes a multipart upload. If versioning is enabled for a bucket, the object version is created upon completion of the multipart upload.
If versioning is enabled for a bucket, a unique versionId is automatically generated for the version of the object being stored. This versionId is also returned in the response using the x-amz-version-id response header.
If versioning is suspended, the object version is stored with a null versionId and if a null version already exists it will be overwritten.
If the bucket where the multipart upload occurs is configured for a platform service, multipart upload succeeds even if the associated replication or notification action fails.
If this occurs, an alarm is raised in the Grid Manager on Total Events (SMTT). The Last Event message displays Failed to publish notifications for bucket-name object key
for the last object whose notification failed. (To see this message, select . View Last Event at the top of the table.) Event messages are also listed in /var/local/log/bycasterr.log.
A tenant can trigger the failed replication or notification by updating the object's metadata or tags. A tenant can resubmit the existing values to avoid making unwanted changes.