[
https://issues.apache.org/jira/browse/HDFS-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046765#comment-13046765
]
Kihwal Lee commented on HDFS-2054:
----------------------------------
To minimum, it will get rid of the annoying stack trace.
transferTo() is not exactly making it easy to deal with different exceptions
differently. I believe things like EAGAIN was fixed now, but to deal with
others you have to parse the error itself, which is rather gross. Ideally we
want to deal with EAGAIN, EPIPE, etc. separately and if something else happens
print an error message.
> BlockSender.sendChunk() prints ERROR for connection closures encountered
> during transferToFully()
> --------------------------------------------------------------------------------------------------
>
> Key: HDFS-2054
> URL: https://issues.apache.org/jira/browse/HDFS-2054
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Affects Versions: 0.22.0, 0.23.0
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Priority: Minor
> Attachments: HDFS-2054.patch
>
>
> The addition of ERROR was part of HDFS-1527. In environments where clients
> tear down FSInputStream/connection before reaching the end of stream, this
> error message often pops up. Since these are not really errors and especially
> not the fault of data node, the message should be toned down at least.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
