[
https://issues.apache.org/jira/browse/HADOOP-19033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808676#comment-17808676
]
Steve Loughran commented on HADOOP-19033:
-----------------------------------------
if the next 3.4 RC is off branch-3.4 I can cherrypick and retest; HADOOP-19027
should go in *first* to avoid merge pain and correct other issues.
Ideally I'd cherrypick the current sequence of -aws changes including the WiP
sdk update (HADOOP-19046), in the same order as they have gone in.
happy to do the work
> S3A: disable checksum validation
> --------------------------------
>
> Key: HADOOP-19033
> URL: https://issues.apache.org/jira/browse/HADOOP-19033
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.4.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.5.0
>
>
> AWS v2 sdk turns on client-side checksum validation; this kills performance
> Given we are using TLS to download from AWS s3, there's implicit channel
> checksumming going on on, that's along with the IPv4 TCP checksumming.
> We don't need it, all it does is slow us down.
> proposed: disable in DefaultS3ClientFactory
> I don't want to add an option to enable it as it only complicates life (yet
> another config option), but I am open to persuasion
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
