-
Notifications
You must be signed in to change notification settings - Fork 592
HDDS-6084. [Multi-Tenant] Handle upgrades to version supporting S3 multi-tenancy #3018
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
d4d6912
HDDS-6084. Handle upgrades to version supporting S3 multi-tenancy
smengcl d6effa7
Weave aspect; Add layout feature limit to tenant read-only requests, …
smengcl 7fcc689
Add annotation to the rest of the tenant write requests.
smengcl 10c3bac
ElementType.CONSTRUCTOR doesn't work; cleanup.
smengcl 32dcfe2
checkLayoutFeature should work with all methods with OM as the first …
smengcl 18ab2aa
Add test; checkstyle.
smengcl 977f1f9
Address test failures.
smengcl 59859ea
Add TODO, auto-generate weaver XML in the future.
smengcl 074dada
Integration test: trigger finalization from the client rather than di…
smengcl c8466ad
Integration check: preFinalizationCheck / cleanup.
smengcl b4010ac
Cleanup addressed comment.
smengcl 57af2cf
More restrictive checking of JoinPoint in checkLayoutFeature.
smengcl 62269f1
Acceptance test: add aws s3api testing before and after upgrade final…
smengcl 3ce0326
QoL: Fix comment syntax in docker-config leading to annoying `WARNING…
smengcl e3baa68
QoL: Fix docker deprecate warning: `--no-ansi` -> `--ansi never`
smengcl 993f1c2
Integration test: Move pre-finalization checks and finalization to cl…
smengcl 6c37edb
Move all create operations to generate; Remove HDDS-6261 repro.
smengcl 47c104c
Create custom key instead of relying on /opt/hadoop/ files.
smengcl File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@smengcl @errose28 maybe I'm missing something, but wouldn't this fail if we actually ran upgrade path test?
https://github.com/adoroszlai/hadoop-ozone/runs/6613025379#step:5:738
I think actual OM MLV for 1.2.0 and 1.2.1 is still 0, regardless of this change.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right.
Though in the latest feature branch it is still 0 (probably fixed when I was resolving conflicts when doing the merge master 3 days ago or some time ago):
https://github.com/smengcl/hadoop-ozone/blob/HDDS-4944/hadoop-ozone/dist/src/main/compose/upgrade/upgrades/non-rolling-upgrade/1.1.0-1.2.0/callback.sh#L47-L49
Not sure why I bumped it when doing this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Anyway, the om version bump in
with_new_version_finalizedis intended. As after the finalization it should be bumped to the latest version. But inpre_finalizedit should still be zero.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But this callback applies when new version is 1.2.0.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was going to say when I was merging master to the feature branch just 3 days ago, I had to bump the
_check_om_mlvsfurther to 3 to pass acceptance (misc):https://github.com/apache/ozone/blame/HDDS-4944/hadoop-ozone/dist/src/main/compose/upgrade/upgrades/non-rolling-upgrade/1.2.1-1.3.0/callback.sh#L74
But then I realized this is the one from 1.1.0 to 1.2.0.
Yup so in this case it should still be zero (in 1.2.0).
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is due to the upgrade test.sh script was actually testing the latest compiled version rather than the actual 1.2.0 at the time, and didn't have 1.2.1-1.3.0 yet. And yes it should be reverted back to 0 now (if I haven't done that yet).
Thanks for catching this @adoroszlai !
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed this in commit: 00a5007 (PR #3450)