You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2015/04/23 23:52:39 UTC

[jira] [Resolved] (HADOOP-11851) s3n to swallow IOEs on inner stream close

     [ https://issues.apache.org/jira/browse/HADOOP-11851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran resolved HADOOP-11851.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.7.1

> 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: Takenori Sato
>            Priority: Minor
>             Fix For: 2.7.1
>
>
> 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)