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 "surendra singh lilhore (JIRA)" <ji...@apache.org> on 2015/04/24 05:33:38 UTC

[jira] [Commented] (HADOOP-11874) s3a can throw spurious IOEs on close()

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

surendra singh lilhore commented on HADOOP-11874:
-------------------------------------------------

I would like to work on this. I will check the code and update the status 

> s3a can throw spurious IOEs on close()
> --------------------------------------
>
>                 Key: HADOOP-11874
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11874
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 2.7.0
>            Reporter: Steve Loughran
>
> from a code review, it's clear that the issue seen in HADOOP-11851 can surface in S3a, though with HADOOP-11570, it's less likely. It will only happen on those cases when abort() isn't called.
> The "clean" close() code path needs to catch IOEs from the wrappedStream and call abort() in that situation too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)