[
https://issues.apache.org/jira/browse/HADOOP-18410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581757#comment-17581757
]
Steve Loughran commented on HADOOP-18410:
-----------------------------------------
setting fs.s3a.input.async.drain.threshold=512G avoids the problem
note how the problem surfaces in different operations. will be tricky to
replicate in a test
{code}
00:43:19.768 ERROR: AnalysisException: getFileStatus on
s3a://impala-test/test-warehouse/tpcds-testcase-data:
com.amazonaws.SdkClientException: Unable to execute HTTP request: Timeout
waiting for connection from pool
00:43:19.768 CAUSED BY: InterruptedIOException: getFileStatus on
s3a://impala-test/test-warehouse/tpcds-testcase-data:
com.amazonaws.SdkClientException: Unable to execute HTTP request: Timeout
waiting for connection from pool
00:43:19.768 CAUSED BY: SdkClientException: Unable to execute HTTP request:
Timeout waiting for connection from pool
00:43:19.768 CAUSED BY: ConnectionPoolTimeoutException: Timeout waiting for
connection from pool
{code}
> S3AInputStream async drain not releasing http connections
> ---------------------------------------------------------
>
> Key: HADOOP-18410
> URL: https://issues.apache.org/jira/browse/HADOOP-18410
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.9
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
>
> Impala tcp-ds setup to s3 is hitting problems with timeout fetching http
> connections from the s3a fs pool. Disabling s3a async drain makes this
> problem *go away*. assumption, either those async ops are blocking, or they
> are not releasing references properly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
