[
https://issues.apache.org/jira/browse/HADOOP-11851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14509210#comment-14509210
]
Steve Loughran commented on HADOOP-11851:
-----------------------------------------
it's similar to HADOOP-11730; that's the overall "recover from failure" code.
This is for {{close()}} to not trigger problems.
HADOOP-11730 is probably a superset.
> s3n to swallow IOEs on inner stream close
> -----------------------------------------
>
> Key: HADOOP-11851
> URL: https://issues.apache.org/jira/browse/HADOOP-11851
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/s3
> Affects Versions: 2.6.0
> Reporter: Steve Loughran
> Assignee: Anu Engineer
> Priority: Minor
>
> We've seen a situation where some work was failing from (recurrent)
> connection reset exceptions.
> Irrespective of the root cause, these were surfacing not in the read
> operations, but when the input stream was being closed -including during a
> seek()
> These exceptions could be caught & logged & warn, rather than trigger
> immediate failures. It shouldn't matter to the next GET whether the last
> stream closed prematurely, as long as the new one works
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
