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

ASF GitHub Bot commented on HADOOP-18410:
-----------------------------------------

steveloughran commented on PR #4766:
URL: https://github.com/apache/hadoop/pull/4766#issuecomment-1221329260

   as this draining code is used in prefetch too, i'm going to
   1. create a StreamDrainer class which the prefetch stream will also switch 
to; this code is fussy and I don't want duplicates
   2. have it implement CallableWithIOE so can be passed in to submit(); no 
need for an extra l-expression to invoke.
   
   the isolation lets me add unit tests for its failure cases
   
   * read returns -1 while data still remaining
   * read() throws ioe
   * remaining finishes while data remaining
   * abort failure




> S3AInputStream.unbuffer() 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: Blocker
>              Labels: pull-request-available
>
> 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]

Reply via email to