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 "Gabor Bota (JIRA)" <ji...@apache.org> on 2018/04/09 10:29:00 UTC
[jira] [Assigned] (HADOOP-15239) S3ABlockOutputStream.flush() be
no-op when stream closed
[ https://issues.apache.org/jira/browse/HADOOP-15239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabor Bota reassigned HADOOP-15239:
-----------------------------------
Assignee: Gabor Bota
> S3ABlockOutputStream.flush() be no-op when stream closed
> --------------------------------------------------------
>
> Key: HADOOP-15239
> URL: https://issues.apache.org/jira/browse/HADOOP-15239
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.9.0, 2.8.3, 2.7.5, 3.0.0
> Reporter: Steve Loughran
> Assignee: Gabor Bota
> Priority: Trivial
>
> when you call flush() on a closed S3A output stream, you get a stack trace.
> This can cause problems in code with race conditions across threads, e.g. FLINK-8543.
> we could make it log@warn "stream closed" rather than raise an IOE. It's just a hint, after all.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org