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/24 12:12:40 UTC
[jira] [Updated] (HADOOP-11874) s3a can throw spurious IOEs on
close()
[ https://issues.apache.org/jira/browse/HADOOP-11874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-11874:
------------------------------------
Issue Type: Sub-task (was: Bug)
Parent: HADOOP-11694
> 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
> Assignee: surendra singh lilhore
>
> 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)