[
https://issues.apache.org/jira/browse/HADOOP-18845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18058175#comment-18058175
]
Ahmar Suhail commented on HADOOP-18845:
---------------------------------------
[[email protected]] [~mthakur] any memory if this every surfaced as
`Caused by: org.apache.http.NoHttpResponseException: The target server failed
to respond`
Hitting these a lot in our clusters, and I think it's because idle connections
are kept around for too long
> Add ability to configure ConnectionTTL of http connections while creating S3
> Client.
> ------------------------------------------------------------------------------------
>
> Key: HADOOP-18845
> URL: https://issues.apache.org/jira/browse/HADOOP-18845
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.6
> Reporter: Mukund Thakur
> Assignee: Mukund Thakur
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.3.9, 3.5.0
>
>
> The option fs.s3a.connection.ttl sets the maximum time an idle connection may
> be retained in the http connection pool.
> A lower value: fewer connections kept open, networking problems related to
> long-lived connections less likely
> A higher value: less time spent negotiating TLS connections when new
> connections are needed
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
