HDDS-14347. Handle upgrades to support S3 lifecycle #9614
+48
−1
Conversation
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
…cycleConfigurationSetRequest
…cycleConfigurationDeleteRequest
chungen0126
reviewed
Jan 10, 2026
Contributor
chungen0126
left a comment
chungen0126
left a comment
There was a problem hiding this comment.
Thanks @YutaLin. Please add some tests for these changes. Also, HDDS-14359 might block this PR because the smoke tests require environment updates for the 2.1.0 to 2.2.0 upgrade.
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?
To ensure safe upgrades and downgrades (rollback) when introducing lifecycle, we need to integrate with the OM Upgrade Framework.
Add OM Layout Feature: Introduce a new OMLayoutFeature (e.g., LIFECYCLE_SUPPORT) to manage the versioning of new lifecycle table.
Block APIs in Pre-finalized State: Reject requests to new lifecycle APIs if the OM is not yet finalized. This prevents state corruption if a rollback occurs
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-14347
How was this patch tested?
CI Pass: https://github.com/YutaLin/ozone/actions/runs/20869524864