[
https://issues.apache.org/jira/browse/HADOOP-13973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved HADOOP-13973.
-------------------------------------
Resolution: Cannot Reproduce
Fix Version/s: 3.1.0
Haven't seen this ourselves, and with the retry logic in reopen() in the input
stream, if the error is translated into an IOE, it will be handled by the S3A
retry policy
> S3A GET/HEAD requests failing: java.lang.IllegalStateException: Connection is
> not open/Connection pool shut down
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-13973
> URL: https://issues.apache.org/jira/browse/HADOOP-13973
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.8.0
> Environment: EC2 cluster
> Reporter: Rajesh Balamohan
> Assignee: Steve Loughran
> Priority: Major
> Fix For: 3.1.0
>
>
> S3 requests failing with an error coming from Http client,
> "java.lang.IllegalStateException: Connection is not open"
> Some online discussion implies that this is related to shared connection pool
> shutdown & fixed in http client 4.4+. Hadoop & AWS SDK use v 4.5.2 so the fix
> is in, we just need to make sure the pool is being set up right.
> There's a problem here of course: it may require moving to a later version of
> the AWS SDK, with the consequences on jackson &c, as seen in HADOOP-13050.
> And that's if there is a patched version out there
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
