[ https://issues.apache.org/jira/browse/HADOOP-15239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16431323#comment-16431323 ]
Gabor Bota edited comment on HADOOP-15239 at 4/13/18 2:21 PM: -------------------------------------------------------------- Tests ran on us-west-2 successfully. Should I submit patches for other branches as well? (2.7.5, 2.8.3, 2.9.0) was (Author: gabor.bota): Tests ran on us-west-2 successfully. Should I submit patches for other as well? (2.7.5, 2.8.3, 2.9.0) > 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