[
https://issues.apache.org/jira/browse/HADOOP-19317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17900134#comment-17900134
]
ASF GitHub Bot commented on HADOOP-19317:
-----------------------------------------
steveloughran opened a new pull request, #7178:
URL: https://github.com/apache/hadoop/pull/7178
New option
fs.s3a.connection.expect.continue
This controls whether or not an PUT request to the S3 store sets the
"Expect: 100-continue" header and awaits a 100 CONTINUE response before
uploading any data.
This allows for throttling and other problems to be detected fast.
The default is "true" -the header is sent.
This is the SDK v1 backport
* setting up old client
* slightly different tests, including flag propagation.
### How was this patch tested?
New tests
### For code changes:
- [X] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [X] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> S3A: fs.s3a.connection.expect.continue controls 100 CONTINUE behavior
> ---------------------------------------------------------------------
>
> Key: HADOOP-19317
> URL: https://issues.apache.org/jira/browse/HADOOP-19317
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.4.1
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.5.0, 3.4.2
>
>
> New option
> {code}
> fs.s3a.connection.expect.continue
> {code}
> This controls whether or not an PUT request to the S3 store
> sets the "Expect: 100-continue" header and awaits a 100 CONTINUE
> response before uploading any data.
> This allows for throttling and other problems to be detected fast.
> The default is "true" -the header is sent.
> It seems like either the AWS SDK or http client libraries underneath don't
> recognise a dead HTTPS connection when using this.
> Leaving as enabled as it can cope with heavy load better (clients can get a
> 503 and know to back off before uploading any data.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
