[
https://issues.apache.org/jira/browse/HADOOP-15239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16459259#comment-16459259
]
Hudson commented on HADOOP-15239:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14094 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14094/])
HADOOP-15239 S3ABlockOutputStream.flush() be no-op when stream closed.
(fabbri: rev 919865a34bd5c3c99603993a0410846a97975869)
* (edit)
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3ABlockOutputStream.java
* (add)
hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/TestS3ABlockOutputStream.java
> 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
> Fix For: 3.2.0
>
> Attachments: HADOOP-15239.001.patch, HADOOP-15239.002.patch
>
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
