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

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

steveloughran opened a new pull request, #7701:
URL: https://github.com/apache/hadoop/pull/7701

   
   HADOOP-19567.
   
   catch all exception raised in stream close; log at debug
   
   <!--
     Thanks for sending a pull request!
       1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
       2. Make sure your PR title starts with JIRA issue id, e.g., 
'HADOOP-17799. Your PR title ...'.
   -->
   
   ### How was this patch tested?
   
   Surfaced during a cloudstore bandwidth test; manual testing can check.
   
   Hard to write an ITest as it probably depends on the stream state at the 
time...will have to explore.
   
   ### For code changes:
   
   - [X] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   




> S3A: error stack traces printed on analytics stream factory close
> -----------------------------------------------------------------
>
>                 Key: HADOOP-19567
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19567
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.4.2
>            Reporter: Steve Loughran
>            Priority: Major
>
> When you close an s3a filesystem there is a lot of ERROR level stack traces 
> about a CancellationException -despite that being exactly what is wanted.
> Core of it comes from netty.
> {code}
>         Suppressed: software.amazon.awssdk.core.exception.SdkClientException: 
> Request attempt 1 failure: Unable to execute HTTP request: The connection was 
> closed during the request. The request will usually succeed on a retry, but 
> if it does not: consider disabling any proxies you have configured, enabling 
> debug logging, or performing a TCP dump to identify the root cause. If this 
> is a streaming operation, validate that data is being read or written in a 
> timely manner. Channel Information: ChannelDiagnostics(channel=[id: 
> 0x801baead, L:0.0.0.0/0.0.0.0:59534 ! 
> R:bucket.vpce-0117f6033eaf7aee5-2hxd9fg4.s3.us-west-2.vpce.amazonaws.com/10.80.134.179:443],
>  channelAge=PT0.676S, requestCount=1, responseCount=0, 
> lastIdleDuration=PT0.006284125S)
> Caused by: java.lang.IllegalStateException: executor not accepting a task
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to