-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
HADOOP-19258: Upgrade aws sdk v2 to 2.27.14 #7015
base: trunk
Are you sure you want to change the base?
Conversation
💔 -1 overall
This message was automatically generated. |
we have to be really rigorous here as there are many regressions which can sneak past the test suites (new log messages on abort(), performance slow downs) which aren't picked up by junit itself. And needless exported dependencies is a recurrent PITA. |
+rebase or merge branch to resolve the conflicts |
efa0fc6
to
1655acc
Compare
💔 -1 overall
This message was automatically generated. |
Testing against a Regular S3 bucket in auth-keys
Scale Tests
adding access point:
Getting a lot of errors, currently debugging: several parsing errors
few encryption errors:
ILoadTest
|
I fixed the assume role issue in #7021 |
regarding the others
Can you just do a checkout of trunk with no changes, run the same tests and see what the results are? |
re-ran the scale tests with and without sdk update commit. I am seeing similar failures in both. Error samples included below. I'll rebase this branch with #7021. I'll also look into ITestS3AConfiguration tests next. without AWS SDK update:command:
With SDK updatecommand : error samples:
|
BTW, @diljotgrewal does this new SDK fix aws/aws-sdk-java-v2#5247 This is a serious problem and nobody seems be giving it attention. It also flags to me that there seems to be more attention in the library to new features over fundamental issues. It'd be nice if you can draw attention to the SDK team about this -the more internal pressure you can generate the more likely it is that someone may actually look at it. |
d8530d3
to
ebc8913
Compare
This SDK is incomplete. It lets you set the flag on put/complete multipart upload, but not on CopyObjectRequest. We need this for rename. Given copy is just a PUT with a different source, I don't see why it shouldn't be available in S3 -so it's just an SDK omission Am I correct? |
💔 -1 overall
This message was automatically generated. |
Just talked to the SDK team, InstanceProfileCredentialsProvider issue is not fixed with this SDK release. It is on their radar and they plan to work on it soon. Re: incomplete SDK: can you please give me some context? Which flag is missing in CopyObjectRequest? |
happy
I couldn't see how to set the If-none-match header on a CopyObjectRequest |
does this address the needless logging of HADOOP-19272? if not, later one is needed and you need to do the before/after checks to make sure things are better not worse -including a rename of a 128+ MB file. Think we should add a large file upload and for anyone testing in EC2 the upload has to go to a s3 store on another continent. if you can think of anything else like this, add it to testing.md as you do it. thanks FYI, we fear SDK updates for subtle regressions like that. They can get past the automated testing but fill up the logs -which is why we absolutely require that step of manual review of all output files of the test run, manual exploratory testing etc. we're going to have to be even more rigorous now. |
@diljotgrewal I've created a feature branch for this work: HADOOP-19256-s3-conditional-writes Can you upgrade to the latest SDK, do the usual qualification work and then submit a request against this branch. I don't want to do any SDK updates to trunk itself until I can come up with a even more robust qualification. Which I think will have to include auditing bits of the SDK as well to see if there are new warnings added. |
Description of PR
Upgrading aws sdk to 2.27.14
How was this patch tested?
Tested with maven in
us-east-1
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?