hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11874) s3a can throw spurious IOEs on close()
Date Thu, 07 Apr 2016 08:26:25 GMT

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

Steve Loughran commented on HADOOP-11874:

no problem. FWIW, I just test against s3 using my own account. provided test teardowns delete
all the s3 files afterwards, cost is nearly nothing

> s3a can throw spurious IOEs on close()
> --------------------------------------
>                 Key: HADOOP-11874
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11874
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          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

View raw message