[
https://issues.apache.org/jira/browse/HDFS-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037031#comment-13037031
]
Joey Echeverria commented on HDFS-1568:
---------------------------------------
I took a look at some more of the logging output. The only problem I see with
e.getMessage() is some common exceptions to provide a message at all. For
example, EOFExceptions seem to rarely have a message. If you do e.toString(),
you'll see both the name of the class and the message (if one was provided).
Let me know how you think I should proceed and I'll submit a new patch.
> Improve DataXceiver error logging
> ---------------------------------
>
> Key: HDFS-1568
> URL: https://issues.apache.org/jira/browse/HDFS-1568
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Joey Echeverria
> Priority: Minor
> Labels: newbie
> Attachments: HDFS-1568-1.patch, HDFS-1568-3.patch,
> HDFS-1568-output-changes.patch
>
>
> In supporting customers we often see things like SocketTimeoutExceptions or
> EOFExceptions coming from DataXceiver, but the logging isn't very good. For
> example, if we get an IOE while setting up a connection to the downstream
> mirror in writeBlock, the IP of the downstream mirror isn't logged on the DN
> side.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
