-
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-19033. S3A: disable checksums when fs.s3a.checksum.validation == false #6441
HADOOP-19033. S3A: disable checksums when fs.s3a.checksum.validation == false #6441
Conversation
ddad17f
to
43b4fb0
Compare
tested s3 london, all good. only failure is the one I see on trunk itself, |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
f950c6f
to
7d57d1f
Compare
LGTM +1 |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
c991f65
to
d3172fc
Compare
rebase problems; will submit fix. latest test runs works except for HADOOP-19037 |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
build is failing from
this is nothing to do with this patch which has got through the maven phase without any problems as well as local testing |
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.
LGTM +1.
Yes yetus failure is unrelated. yesterday's yetus was fine, so we are good.
Merge conflicts needs to be fixed though.
need to rebase as the imports from the error handing pr conflict |
…== false Add new option fs.s3a.checksum.validation, default false, which is used when creating s3 clients to enable/disable checksum validation. When false, GET response processing is measurably faster. Includes a test in ITestS3AOpenCost to validate that disabling works. Change-Id: Ibb826e27bd8801e9323bdddd505c5bc4e0760039
Change-Id: I6298c307bc73f96212dcb229ded0eb1a767247ac
Change-Id: Id1e2d9bbb7785e8e91885da1f3acabd54cefa052
5faad0a
to
45adbb7
Compare
retested, all good except when I ran the openfile cost test with -Dprefetch, which was from #6425. Filed HADOOP-19043 for that |
🎊 +1 overall
This message was automatically generated. |
…= false (#6441) Add new option fs.s3a.checksum.validation, default false, which is used when creating s3 clients to enable/disable checksum validation. When false, GET response processing is measurably faster. Contributed by Steve Loughran.
…= false (#6441) Add new option fs.s3a.checksum.validation, default false, which is used when creating s3 clients to enable/disable checksum validation. When false, GET response processing is measurably faster. Contributed by Steve Loughran.
…= false (apache#6441) Add new option fs.s3a.checksum.validation, default false, which is used when creating s3 clients to enable/disable checksum validation. When false, GET response processing is measurably faster. Contributed by Steve Loughran.
HADOOP-19033. S3A: disable checksums when fs.s3a.checksum.validation == false
Add new option fs.s3a.checksum.validation, default false, which
is used when creating s3 clients.
There's two interceptors in fs.s3a.audit.interceptors to assist
here but it turns out they aren't needed. Retained in case they are,
but we could cut them.
How was this patch tested?
Add a test in ITestS3AOpenCost to validate that disabling works.
This has to use reflection to walk down the sdk filter stream chain; when checksums are
enabled it fails because the bottom stream in the chain is one of the two checksum
validating streams.
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?