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

Gabor Bota commented on HADOOP-15239:
-------------------------------------

If there's a need I also created a test for it. You can check it in this 
commit: 
https://github.com/bgaborg/hadoop/commit/58508d484576a5ee752a1310d0946bfa9f7cf9e7

If a test is needed for this fix, I can upload this as a patch.

> 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
>         Attachments: HADOOP-15239.001.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

Reply via email to