hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13973) S3A get requests failing: java.lang.IllegalStateException: Connection is not open
Date Thu, 16 Feb 2017 13:36:41 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869924#comment-15869924

Steve Loughran commented on HADOOP-13973:

Later httpclients move to ConnectionClosedException. A cause is possibly/probably us calling
abort() on a connection which is still in the pool, and so being picked up again

> S3A get requests failing: java.lang.IllegalStateException: Connection is not open
> ---------------------------------------------------------------------------------
>                 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
>             Fix For: 2.8.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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message