[
https://issues.apache.org/jira/browse/HDFS-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13684163#comment-13684163
]
Steve Loughran commented on HDFS-4906:
--------------------------------------
# having an explicit exception class would aid both testing and (some)
diagnostics. the NIO {{ClosedChannelException}} looks like a good one for re-use
# this could be an opportunity to make the close operation thread-safe. I'd
propose: close() to be synchronized, checkClosed() to act on a volatile boolean
so that the check overhead is less. There'd still be a race condition of
someone trying to write while the close was going on in parallel, but at least
changes would propagate over threads better.
> HDFS Output streams should not accept writes after being closed
> ---------------------------------------------------------------
>
> Key: HDFS-4906
> URL: https://issues.apache.org/jira/browse/HDFS-4906
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Affects Versions: 2.0.5-alpha
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Attachments: HDFS-4906.patch, HDFS-4906.patch
>
>
> Currently if one closes an OutputStream obtained from FileSystem#create and
> then calls write(...) on that closed stream, the write will appear to succeed
> without error though no data will be written to HDFS. A subsequent call to
> close will also silently appear to succeed. We should make it so that
> attempts to write to closed streams fails fast.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
