[
https://issues.apache.org/jira/browse/HADOOP-19317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897762#comment-17897762
]
ASF GitHub Bot commented on HADOOP-19317:
-----------------------------------------
mukund-thakur commented on code in PR #7134:
URL: https://github.com/apache/hadoop/pull/7134#discussion_r1838824224
##########
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/connecting.md:
##########
@@ -150,7 +150,19 @@ If you are working with third party stores, please check
[third party stores in
See [Timeouts](performance.html#timeouts).
-### <a name="networking"></a> Low-level Network Options
+### <a name="networking"></a> Low-level Network/Http Options
+
+The S3A connector uses [Apache HttpClient](https://hc.apache.org/index.html)
to connect to
+S3 Stores.
+The client is configured to create a pool of HTTP connections with S3, so that
once
+the initial set of connections have been made they can re-used for followup
operations.
Review Comment:
*they can be
> S3A: add option to enable/disable 100 CONTINUE
> ----------------------------------------------
>
> 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
>
> Add an option to turn off the HTTP 100 CONTINUE mechanism on PUT requests as
> 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]
