HDDS-16087. Update document for AbortIncompleteMultipartUpload action - #525
Merged
Conversation
priyeshkaratha
force-pushed
the
HDDS-16087
branch
from
August 11, 2026 05:06
c38d502 to
0e99919
Compare
ChenSammi
approved these changes
Aug 17, 2026
ChenSammi
left a comment
ChenSammi
left a comment
Contributor
There was a problem hiding this comment.
Thanks @priyeshkaratha .
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Update the S3 lifecycle documentation to mark AbortIncompleteMultipartUpload as supported in the S3 lifecycle action compatibility table and add a dedicated AbortIncompleteMultipartUpload Action section describing the
DaysAfterInitiationelement with an example lifecycle rule. Document its interaction withMultipartUploadCleanupService: although both services can clean up stale multipart uploads (MPUs),MultipartUploadCleanupServiceruns unconditionally across the cluster, meaning a lifecycle rule withDaysAfterInitiation >= ozone.om.open.mpu.expire.thresholdwould be silently preempted. To prevent this configuration from being ineffective, Ozone rejects such lifecycle configurations atPutBucketLifecycleConfigurationtime. Also addozone.om.open.mpu.expire.thresholdto the Configuration table, describing it as the upper bound forDaysAfterInitiation, and include the same constraint in the Considerations section for quick reference.What is the link to the Apache Jira?
HDDS-16087
How was this patch tested?
Tested manually
